Triple
T35419734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeffrey Skiles |
E1023747
|
entity |
| Predicate | aircraftTypeOnNotableFlight |
P1524
|
FINISHED |
| Object | Airbus A320-214 |
—
|
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: Airbus A320-214 | Statement: [Jeffrey Skiles, aircraftTypeOnNotableFlight, Airbus A320-214]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftTypeOnNotableFlight Context triple: [Jeffrey Skiles, aircraftTypeOnNotableFlight, Airbus A320-214]
-
A.
referredAircraftNotableFeature
Indicates that a referenced aircraft is associated with a notable or distinguishing feature.
-
B.
officiallyFlownOn
Indicates that something has been formally carried or transported aboard a specific flight or aircraft under official or authorized status.
-
C.
aircraftType
chosen
Indicates the specific model or category of aircraft associated with an entity or event.
-
D.
subjectAircraftNotableVariant
Indicates that the subject aircraft has a notable or significant variant related to it.
-
E.
notableTransportAircraft
Indicates that the subject is a transport aircraft recognized for particular significance, such as historical importance, performance, or impact on aviation.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79588cf848190b078b1dfb65da937 |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.