Triple
T20874115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suspended Looping Coaster |
E513971
|
entity |
| Predicate | trackProfile |
P3832
|
FINISHED |
| Object | twisting and looping 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: twisting and looping track | Statement: [Suspended Looping Coaster, trackProfile, twisting and looping track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackProfile Context triple: [Suspended Looping Coaster, trackProfile, twisting and looping track]
-
A.
track
Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
-
B.
trackRecordTrack
Indicates that one entity serves as a record or log that tracks the performance, history, or outcomes associated with another entity.
-
C.
trackType
chosen
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
D.
trackGauge
Indicates the distance between the inner faces of the rails in a railway track system.
-
E.
trackPattern
Indicates that one entity follows, monitors, or records the behavior or state of another according to a defined pattern or sequence.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c46639308190a616193f3975d453 |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.