Triple
T28062363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 339th Fighter Group, USAAF |
E709147
|
entity |
| Predicate | usedAircraftEngineType |
P38991
|
FINISHED |
| Object | piston-engine 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: piston-engine fighters | Statement: [339th Fighter Group, USAAF, usedAircraftEngineType, piston-engine fighters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAircraftEngineType Context triple: [339th Fighter Group, USAAF, usedAircraftEngineType, piston-engine fighters]
-
A.
aircraftEngineType
chosen
Indicates the specific type or classification of engine that an aircraft uses.
-
B.
aircraftPowerplantType
Indicates the type or category of powerplant (e.g., engine or propulsion system) used by an aircraft.
-
C.
aircraftEngineTypeProduced
Indicates that a particular type of aircraft engine is manufactured or produced by a specified entity.
-
D.
usedByAircraftType
Indicates that something (such as equipment, infrastructure, or a procedure) is employed or operated by a specific type or category of aircraft.
-
E.
usedOnAircraftName
Indicates that something is employed or applied on an aircraft identified by a specific name.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 27, 2026, 8:40 p.m.