Triple
T34072958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Aero Engines |
E873822
|
entity |
| Predicate | roleOfRolls-Royce |
P183148
|
FINISHED |
| Object | former shareholder |
—
|
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: former shareholder | Statement: [International Aero Engines, roleOfRolls-Royce, former shareholder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfRolls-Royce Context triple: [International Aero Engines, roleOfRolls-Royce, former shareholder]
-
A.
roleAtMercedes
Indicates that an entity holds or held a specific role or position at Mercedes.
-
B.
carCultureRole
Indicates the role or function an entity has within car culture, such as how it contributes to or is perceived in automotive-related communities, practices, or values.
-
C.
roleInEngine
Indicates the specific function or responsibility an entity has within an engine or engine-like system.
-
D.
roleInTesla
Indicates that one entity holds or held a specific role, position, or function within the organization Tesla.
-
E.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f798387ea481909f51303f53a22e52 |
completed | May 3, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79798663481908d6bc48dd6a94ca6 |
completed | May 3, 2026, 6:44 p.m. |
Created at: May 1, 2026, 1:52 a.m.