Triple
T33095330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flagon |
E846892
|
entity |
| Predicate | subjectAircraftEra |
P66519
|
FINISHED |
| Object | Cold War military aviation |
—
|
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: Cold War military aviation | Statement: [Flagon, subjectAircraftEra, Cold War military aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectAircraftEra Context triple: [Flagon, subjectAircraftEra, Cold War military aviation]
-
A.
aircraftEra
chosen
Indicates the historical time period or era during which an aircraft was designed, produced, or primarily operated.
-
B.
airlineEra
Indicates the historical time period or era during which an airline operated or was active.
-
C.
aircraftGeneration
Indicates a generational relationship between aircraft, such as one model being a successor, predecessor, or belonging to a specific generation relative to another.
-
D.
airfieldEra
Indicates the historical time period or era during which an airfield was active, used, or relevant.
-
E.
historicalAircraftRole
Indicates the role or function an aircraft historically served, such as its operational or mission type in past contexts.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 1, 2026, 1:26 a.m.