Triple
T31817428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McDonnell Douglas KC-10 Extender |
E812173
|
entity |
| Predicate | airRefuelingOperator |
P172930
|
FINISHED |
| Object | boom operator |
—
|
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: boom operator | Statement: [McDonnell Douglas KC-10 Extender, airRefuelingOperator, boom operator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airRefuelingOperator Context triple: [McDonnell Douglas KC-10 Extender, airRefuelingOperator, boom operator]
-
A.
airBaseOperator
Indicates that one entity operates, manages, or is responsible for running an air base used for aviation activities.
-
B.
airRefuellingMethod
Indicates the method or technique used to transfer fuel between aircraft during in-flight refuelling.
-
C.
canBeAerialRefueled
Indicates that one entity has the capability to receive fuel from another entity while in flight through aerial refueling operations.
-
D.
usedAerialRefueling
Indicates that one entity received fuel in flight from another entity via aerial refueling.
-
E.
aircraftTanker
Indicates that one aircraft is serving as an aerial refueling tanker for another aircraft.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 30, 2026, 11:45 p.m.