Triple
T17396673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safran Aircraft Engines |
E422971
|
entity |
| Predicate | roleInCFMInternational |
P127319
|
FINISHED |
| Object | co-owner |
—
|
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: co-owner | Statement: [Safran Aircraft Engines, roleInCFMInternational, co-owner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCFMInternational Context triple: [Safran Aircraft Engines, roleInCFMInternational, co-owner]
-
A.
referredAircraftRole
Indicates that one aircraft is mentioned or designated in relation to another aircraft’s role, function, or status within a specific context or event.
-
B.
businessRoleOfSidLuft
Indicates that the subject holds or held a business-related role or position in relation to Sid Luft.
-
C.
hasRoleInAviation
Indicates that an entity holds or has held a specific role, position, or function within the field of aviation.
-
D.
usedByAirlineRole
Indicates that something (such as a resource, system, or process) is utilized by a specific role or position within an airline organization.
-
E.
airlineAllianceRole
Indicates the specific role or function an airline holds within an airline alliance.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43abd9b748190bd55c863276d9e3a |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:45 a.m.