Triple
T13188958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cold War naval aviation |
E313930
|
entity |
| Predicate | majorAircraftType |
P45618
|
FINISHED |
| Object | carrier-based fighters |
—
|
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: carrier-based fighters | Statement: [Cold War naval aviation, majorAircraftType, carrier-based fighters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorAircraftType Context triple: [Cold War naval aviation, majorAircraftType, carrier-based fighters]
-
A.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
B.
typicalAircraftTypeCategory
chosen
Indicates the general class or category of aircraft type that is most commonly associated with or used in a given context.
-
C.
poweredAircraftType
Indicates that one entity is a type or category of aircraft that is propelled by an onboard power source (e.g., engines), as opposed to being unpowered.
-
D.
commonAircraftFamily
Indicates that two aircraft belong to the same aircraft family or series, sharing a common design lineage.
-
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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:15 p.m.