Triple
T4341786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakajima Sakae radial engine |
E97797
|
entity |
| Predicate | aircraftCategoryPowered |
P8254
|
FINISHED |
| Object | single-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: single-engine fighters | Statement: [Nakajima Sakae radial engine, aircraftCategoryPowered, single-engine fighters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftCategoryPowered Context triple: [Nakajima Sakae radial engine, aircraftCategoryPowered, single-engine fighters]
-
A.
notableAircraftPowered
chosen
Indicates that an aircraft is notably powered or propelled by a specified engine, powerplant, or propulsion system.
-
B.
typicalAircraftTypeCategory
Indicates the general class or category of aircraft type that is most commonly associated with or used in a given context.
-
C.
aircraft
Indicates that an entity is an aircraft or functions in the role of an aircraft in the described context.
-
D.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
E.
developedAircraft
Indicates that an entity (such as a person or organization) was responsible for designing, creating, or engineering a particular aircraft.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351878c148190b384053479d41caf |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:14 p.m.