Triple
T9795597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Odyssey of Flight 33 |
E237708
|
entity |
| Predicate | aircraftTypeInStory |
P1524
|
FINISHED |
| Object | jet airliner |
—
|
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: jet airliner | Statement: [The Odyssey of Flight 33, aircraftTypeInStory, jet airliner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftTypeInStory Context triple: [The Odyssey of Flight 33, aircraftTypeInStory, jet airliner]
-
A.
aircraftType
chosen
Indicates the specific model or category of aircraft associated with an entity or event.
-
B.
typicalAircraftTypeCategory
Indicates the general class or category of aircraft type that is most commonly associated with or used in a given context.
-
C.
intendedAircraft
Indicates that an aircraft is the one planned or designated to be used for a particular flight, mission, or operation.
-
D.
basedOnAircraft
Indicates that one entity is derived from, modeled after, or otherwise uses a particular aircraft as its basis or primary reference.
-
E.
homeToAircraftType
Indicates that a location serves as a base or primary operating home for a particular type of aircraft.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda34916dc8190acef2ba003e56a33 |
completed | April 1, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:28 p.m.