Triple
T20874119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suspended Looping Coaster |
E513971
|
entity |
| Predicate | riderOrientation |
P122172
|
FINISHED |
| Object | forward-facing seats |
—
|
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: forward-facing seats | Statement: [Suspended Looping Coaster, riderOrientation, forward-facing seats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riderOrientation Context triple: [Suspended Looping Coaster, riderOrientation, forward-facing seats]
-
A.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
B.
typicalRiderOrientation
chosen
Indicates the usual or standard physical position or alignment a rider maintains relative to what they are riding.
-
C.
ridingPosition
Indicates the relative physical placement or posture of an entity while it is riding or being carried by another entity.
-
D.
locationOrientation
Indicates how one entity is spatially oriented or positioned relative to a specific location or reference point.
-
E.
orientationType
Indicates the specific kind or category of orientation relationship that exists between entities (such as spatial, directional, or alignment-based orientation).
- 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.