Triple
T24131363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce BR710 |
E597960
|
entity |
| Predicate | roleOnBoeing717 |
P154957
|
FINISHED |
| Object | rear-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: rear-fuselage-mounted engine | Statement: [Rolls-Royce BR710, roleOnBoeing717, rear-fuselage-mounted engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnBoeing717 Context triple: [Rolls-Royce BR710, roleOnBoeing717, rear-fuselage-mounted engine]
-
A.
roleWithinBoeing
Indicates that one entity holds or has held a specific role, position, or function within the organization Boeing.
-
B.
roleInAirbus
Indicates that an entity holds or has held a specific role or position within Airbus.
-
C.
roleInCFMInternational
Indicates that an entity holds a specific role or position within the organization CFM International.
-
D.
hasRoleInAviation
Indicates that an entity holds or has held a specific role, position, or function within the field of aviation.
-
E.
businessRoleOfSidLuft
Indicates that the subject holds or held a business-related role or position in relation to Sid Luft.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7788788190a71ad080fc2890a8 |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 11:25 p.m.