Triple
T1684631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta One |
E36414
|
entity |
| Predicate | seatRecline |
P32733
|
FINISHED |
| Object | 180 degrees |
—
|
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: 180 degrees | Statement: [Delta One, seatRecline, 180 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatRecline Context triple: [Delta One, seatRecline, 180 degrees]
-
A.
seatLocation
Indicates the spatial position or placement of a seat relative to a reference point or environment.
-
B.
seatingPosition
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.
seatPitch
Indicates the distance between a seat and the seat directly in front of it, typically measuring legroom or spacing in a seating arrangement.
-
D.
seatOnBody
Indicates that one entity functions as a seat or seating surface that is physically attached or integrated to a body or body-like structure.
-
E.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
- F. None of above. chosen
Provenance (4 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aba644070c81908745b56d981fe273 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61b57a6881909373af287ef24799 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aba641e6a881909645577e72b53df2 |
completed | March 7, 2026, 4:14 a.m. |
Created at: March 4, 2026, 7:29 p.m.