Triple
T31169318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morning Bell/Amnesiac |
E794559
|
entity |
| Predicate | followsTrackOnAmnesiac |
P25512
|
FINISHED |
| Object | Like Spinning Plates |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Like Spinning Plates | Statement: [Morning Bell/Amnesiac, followsTrackOnAmnesiac, Like Spinning Plates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsTrackOnAmnesiac Context triple: [Morning Bell/Amnesiac, followsTrackOnAmnesiac, Like Spinning Plates]
-
A.
followsInTracklist
chosen
Indicates that one item directly comes after another in an ordered tracklist sequence.
-
B.
trackOn
Indicates that one entity is physically positioned or moving along the surface or path of another, like a vehicle on a track or rails.
-
C.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
-
D.
trackFrom
Indicates a source or origin from which something is tracked or monitored.
-
E.
track
Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 29, 2026, 9:07 p.m.