Triple
T5079317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying Coaster |
E114475
|
entity |
| Predicate | hasTrainPositionRelativeToTrack |
P20526
|
FINISHED |
| Object | below track |
—
|
LITERAL FINISHED |
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: below track | Statement: [Flying Coaster, hasTrainPositionRelativeToTrack, below track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainPositionRelativeToTrack Context triple: [Flying Coaster, hasTrainPositionRelativeToTrack, below track]
-
A.
positionInTrackList
Indicates the specific ordered place an item occupies within a track list.
-
B.
relativePositionOnCourse
chosen
Indicates the positional relationship of one participant or object relative to another along a defined course or route.
-
C.
hasNearbyRailway
Indicates that one entity is located close to a railway associated with or relevant to another entity.
-
D.
hasPositionOn
Indicates that one entity occupies or holds a specific role, job, or spatial location relative to another entity.
-
E.
isPositionOf
Indicates that one entity represents the spatial or organizational position or location of another entity.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74f75cf0819088be9e076eaf3168 |
completed | March 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.