Triple
T10188378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ER4 |
E236968
|
entity |
| Predicate | aircraftEngineMounting |
P92607
|
FINISHED |
| Object | rear-fuselage mounted |
—
|
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: rear-fuselage mounted | Statement: [ER4, aircraftEngineMounting, rear-fuselage mounted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftEngineMounting Context triple: [ER4, aircraftEngineMounting, rear-fuselage mounted]
-
A.
wingMountedEngines
Indicates that the engines of an aircraft are mounted on its wings rather than on other parts of the airframe.
-
B.
aircraftEngineType
Indicates the specific type or classification of engine that an aircraft uses.
-
C.
typicalTurbineMounting
Indicates the usual or standard way in which a turbine is mounted or installed relative to its supporting structure.
-
D.
aircraftPowerplantType
Indicates the type or category of powerplant (e.g., engine or propulsion system) used by an aircraft.
-
E.
hardpoints
Indicates a relationship where one entity provides designated attachment locations or mounting interfaces on its structure for connecting other components or equipment.
- F. None of above. chosen
Provenance (4 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded7c3278819093312665b54d888c |
completed | April 2, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69cd7edc6cf081909d95859d880a4059 |
completed | April 1, 2026, 8:23 p.m. |
Created at: March 30, 2026, 9:12 p.m.