Triple
T14684589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DC Rivals HyperCoaster |
E344876
|
entity |
| Predicate | backwardsSeatsLocation |
P22103
|
FINISHED |
| Object | last row of train |
—
|
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: last row of train | Statement: [DC Rivals HyperCoaster, backwardsSeatsLocation, last row of train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backwardsSeatsLocation Context triple: [DC Rivals HyperCoaster, backwardsSeatsLocation, last row of train]
-
A.
seatLocation
Indicates the spatial position or placement of a seat relative to a reference point or environment.
-
B.
seatingPosition
chosen
Indicates the relative location or arrangement of an entity’s seat with respect to other seats or a reference point in a seating layout.
-
C.
laterSeat
Indicates that one entity is seated in a position that comes after another entity in a specified ordering or sequence of seats.
-
D.
seatLocatedIn
Indicates that a seat is situated within or belongs to a specific location or area.
-
E.
seatSince
Indicates that an entity has held a particular seat, position, or place continuously since a specified point in 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb56bdb8081909ff86440ba20fb1f |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.