Triple
T21155285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vesna Vulović |
E521296
|
entity |
| Predicate | positionInAircraft |
P17750
|
FINISHED |
| Object | cabin crew member on JAT Flight 367 |
—
|
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: cabin crew member on JAT Flight 367 | Statement: [Vesna Vulović, positionInAircraft, cabin crew member on JAT Flight 367]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInAircraft Context triple: [Vesna Vulović, positionInAircraft, cabin crew member on JAT Flight 367]
-
A.
locationOnAircraft
chosen
Indicates that one entity is physically situated on or within an aircraft.
-
B.
positionOnFlight
Indicates the specific seat or positional assignment that an entity has on a particular flight.
-
C.
typicalPilotPosition
Indicates the usual or standard spatial position or placement where a pilot is located relative to the associated object or system.
-
D.
positionRelativeToTopFlight
Indicates the relative vertical placement of something with respect to the topmost flight (e.g., of stairs or levels).
-
E.
fuselagePosition
Indicates the spatial placement or alignment of a fuselage relative to a reference frame or other aircraft components.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7252b40ac81908ab7e30c662a6c94 |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:58 p.m.