Triple
T36021630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DBR-1 |
E1042003
|
entity |
| Predicate | eraOfSubjectAircraft |
P179858
|
FINISHED |
| Object | Cold War |
—
|
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: Cold War | Statement: [DBR-1, eraOfSubjectAircraft, Cold War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfSubjectAircraft Context triple: [DBR-1, eraOfSubjectAircraft, Cold War]
-
A.
eraOfDesignatedAircraft
chosen
Indicates the historical time period or era during which the designated aircraft was primarily designed, developed, or in standard operational use.
-
B.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
C.
operatorOfReferencedAircraft
Indicates that one entity serves as the operator (e.g., managing or controlling party) of an aircraft that is referenced elsewhere in the context.
-
D.
intendedAircraft
Indicates that an aircraft is the one planned or designated to be used for a particular flight, mission, or operation.
-
E.
typeOfAviation
Indicates the specific category or kind of aviation to which an entity belongs (e.g., commercial, military, private).
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:07 p.m.