Triple
T24465454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 367-80 |
E616954
|
entity |
| Predicate | militaryDerivative |
P156201
|
FINISHED |
| Object | KC-135 Stratotanker |
—
|
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: KC-135 Stratotanker | Statement: [Boeing 367-80, militaryDerivative, KC-135 Stratotanker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryDerivative Context triple: [Boeing 367-80, militaryDerivative, KC-135 Stratotanker]
-
A.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
B.
militaryDomain
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or context.
-
C.
militaryBacked
Indicates that one entity is supported, protected, or sustained by the military power or armed forces of another entity.
-
D.
eraOfPrimaryMilitaryUse
Indicates the historical time period during which the subject was primarily used for military purposes.
-
E.
militaryIssue
Indicates that one entity formally provides or distributes military-related items, orders, or directives to another entity.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298cd2a748190bbb4634e879d89f2 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:19 a.m.