Triple
T9646031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KC-10 Extender |
E233196
|
entity |
| Predicate | refuelingSystems |
P51382
|
FINISHED |
| Object | flying boom |
—
|
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: flying boom | Statement: [KC-10 Extender, refuelingSystems, flying boom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refuelingSystems Context triple: [KC-10 Extender, refuelingSystems, flying boom]
-
A.
refuellingSystem
chosen
Indicates a system or mechanism used to supply fuel from one entity to another.
-
B.
fuelSystem
Indicates a relationship where one entity serves as the fuel system (or part of it) that supplies, stores, or manages fuel for the operation of another entity.
-
C.
propellantFeedSystem
Indicates a relationship where a system supplies, regulates, or transports propellant to a propulsion or engine unit.
-
D.
hasRefuelingSystemSupplier
Indicates that one entity serves as the supplier or provider of the refueling system for another entity.
-
E.
propellantStorage
Indicates that one entity serves as a location or facility where propellant is stored for later use.
- 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_69ca848b31648190b57aa55da20285be |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b8122148190bd0af3a04b21e53e |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:12 p.m.