Triple
T24168001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vought |
E599046
|
entity |
| Predicate | aircraftUsedInConflict |
P69220
|
FINISHED |
| Object | World War II |
E32
|
NE 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: World War II | Statement: [Vought, aircraftUsedInConflict, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftUsedInConflict Context triple: [Vought, aircraftUsedInConflict, World War II]
-
A.
notableAircraftTheater
chosen
Indicates that an aircraft is notably associated with operations or service in a particular theater of activity or conflict.
-
B.
notableAircraftUsed
Indicates that an entity is known for using, operating, or being associated with a particular aircraft in a notable or significant way.
-
C.
historicalAircraftOperated
Indicates that an entity previously operated a specific aircraft model during a past period, but no longer does so.
-
D.
aircraftTypesUsedOn
Indicates the types or models of aircraft that are used on or assigned to a particular route, service, operation, or context.
-
E.
aircraftFlown
Indicates that an entity (typically a person or organization) operates or pilots a particular aircraft.
- F. None of above.
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_69e288cbd62881909de32ca64a70c17b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0facfda3948190b81158cae100d367 |
completed | May 22, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:33 p.m.