Triple
T38619201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swift F.7 |
E936820
|
entity |
| Predicate | aircraftEnginePlacement |
P22132
|
FINISHED |
| Object | fuselage-mounted engine |
—
|
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: fuselage-mounted engine | Statement: [Swift F.7, aircraftEnginePlacement, fuselage-mounted engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftEnginePlacement Context triple: [Swift F.7, aircraftEnginePlacement, fuselage-mounted engine]
-
A.
aircraftEngineMounting
Indicates that an aircraft engine is attached or secured to a supporting structure or mounting point on the aircraft.
-
B.
aircraftEngineType
Indicates the specific type or classification of engine that an aircraft uses.
-
C.
enginePlacement
chosen
Indicates the spatial or structural position where an engine is located or mounted relative to another object or system.
-
D.
wingMountedEngines
Indicates that the engines of an aircraft are mounted on its wings rather than on other parts of the airframe.
-
E.
aircraftPowerplantType
Indicates the type or category of powerplant (e.g., engine or propulsion system) used by an 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.