Triple
T29370662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Dawson |
E744843
|
entity |
| Predicate | flightPassengerOn |
P881
|
FINISHED |
| Object | Oceanic Airlines Flight 815 |
—
|
NE NERFINISHED |
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: Oceanic Airlines Flight 815 | Statement: [Michael Dawson, flightPassengerOn, Oceanic Airlines Flight 815]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightPassengerOn Context triple: [Michael Dawson, flightPassengerOn, Oceanic Airlines Flight 815]
-
A.
passengerFlight
Indicates a relationship where a flight is specifically operated to transport passengers rather than cargo or other purposes.
-
B.
positionOnFlight
Indicates the specific seat or positional assignment that an entity has on a particular flight.
-
C.
passengers
chosen
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
-
D.
boardingFor
Indicates that one entity serves as the designated boarding location or facility for another entity, such as passengers or animals.
-
E.
flightOver
Indicates that one entity moves through the air above or across another entity or area.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669aa3a788190ace4f8d5edbe0708 |
completed | May 2, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:26 p.m.