Triple
T24137991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce BR715 |
E598141
|
entity |
| Predicate | nacelleLocation |
P17750
|
FINISHED |
| Object | rear-fuselage-mounted on Boeing 717 |
—
|
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 on Boeing 717 | Statement: [Rolls-Royce BR715, nacelleLocation, rear-fuselage-mounted on Boeing 717]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nacelleLocation Context triple: [Rolls-Royce BR715, nacelleLocation, rear-fuselage-mounted on Boeing 717]
-
A.
typicalTurbineMounting
Indicates the usual or standard way in which a turbine is mounted or installed relative to its supporting structure.
-
B.
hasTurbineHall
Indicates that something includes or is equipped with a turbine hall as part of its structure or facilities.
-
C.
hasTurbines
Indicates that one entity is equipped with, contains, or includes one or more turbines in relation to another entity.
-
D.
powertrainLocation
Indicates the physical placement or mounting position of a vehicle’s powertrain relative to the rest of the vehicle.
-
E.
locationOnAircraft
chosen
Indicates that one entity is physically situated on or within 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7e3c20819099ff289789829d7e |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:27 p.m.