Triple
T32194035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Officer Craig |
E822350
|
entity |
| Predicate | positionOnAircraft |
P197854
|
FINISHED |
| Object | second-in-command |
—
|
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: second-in-command | Statement: [First Officer Craig, positionOnAircraft, second-in-command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnAircraft Context triple: [First Officer Craig, positionOnAircraft, second-in-command]
-
A.
locationOnAircraft
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.
positionAtAirline
Indicates that an entity holds a specific role or job position within a particular airline.
-
E.
fuselagePosition
Indicates the spatial placement or alignment of a fuselage relative to a reference frame or other aircraft components.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
| PDg | Predicate description generation | batch_69feb3419158819082f4666077535ca9 |
completed | May 9, 2026, 4:08 a.m. |
Created at: May 1, 2026, 12:35 a.m.