Triple
T8946394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engine Alliance GP7200 |
E213230
|
entity |
| Predicate | aircraftEnginePosition |
P22998
|
FINISHED |
| Object | underwing podded 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: underwing podded engine | Statement: [Engine Alliance GP7200, aircraftEnginePosition, underwing podded engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftEnginePosition Context triple: [Engine Alliance GP7200, aircraftEnginePosition, underwing podded engine]
-
A.
aircraftEngineType
Indicates the specific type or classification of engine that an aircraft uses.
-
B.
fuselagePosition
Indicates the spatial placement or alignment of a fuselage relative to a reference frame or other aircraft components.
-
C.
wingMountedEngines
chosen
Indicates that the engines of an aircraft are mounted on its wings rather than on other parts of the airframe.
-
D.
aircraftPowerplantType
Indicates the type or category of powerplant (e.g., engine or propulsion system) used by an aircraft.
-
E.
aircraftEngineManufacturer
Indicates that one entity is the manufacturer of the aircraft engine used by another entity.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66dd00c481908ff20fd66c1954cc |
completed | April 1, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.