Triple
T8946406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engine Alliance GP7200 |
E213230
|
entity |
| Predicate | aircraftEngineCountPerAircraft |
P3542
|
FINISHED |
| Object | four engines on Airbus A380 |
—
|
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: four engines on Airbus A380 | Statement: [Engine Alliance GP7200, aircraftEngineCountPerAircraft, four engines on Airbus A380]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftEngineCountPerAircraft Context triple: [Engine Alliance GP7200, aircraftEngineCountPerAircraft, four engines on Airbus A380]
-
A.
numberOfEngines
chosen
Indicates the quantity of engines associated with or used by an entity.
-
B.
aircraftEngineType
Indicates the specific type or classification of engine that an aircraft uses.
-
C.
aircraftPowerplantType
Indicates the type or category of powerplant (e.g., engine or propulsion system) used by an aircraft.
-
D.
wingMountedEngines
Indicates that the engines of an aircraft are mounted on its wings rather than on other parts of the airframe.
-
E.
aircraftEngineTypeProduced
Indicates that a particular type of aircraft engine is manufactured or produced by a specified 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.