Triple
T29941395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio Tinto aluminum smelter |
E760507
|
entity |
| Predicate | hasCorporateHead |
P50969
|
FINISHED |
| Object | Rio Tinto Group |
—
|
NE NERFINISHED |
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: Rio Tinto Group | Statement: [Rio Tinto aluminum smelter, hasCorporateHead, Rio Tinto Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorporateHead Context triple: [Rio Tinto aluminum smelter, hasCorporateHead, Rio Tinto Group]
-
A.
companyHeaded
Indicates that one entity serves as the leader or chief executive in charge of directing and managing the other entity (the company).
-
B.
hasCorporateOffice
Indicates that an entity maintains a formal corporate office at a specified location or within another organizational entity.
-
C.
haveExecutiveHead
chosen
Indicates that one entity serves as the executive leader or chief authority (e.g., CEO, president, head of government) of another entity.
-
D.
hasHeadquartersRoleFor
Indicates that an entity holds a specific role or position within the headquarters of another entity.
-
E.
parentOrganizationHeadquartered
Indicates that the parent organization has its main headquarters located in the specified place.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a00bc079314819096271bba60bee52d |
completed | May 10, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_6a00bba5bd408190ace5db0c4a90dc6f |
completed | May 10, 2026, 5:08 p.m. |
Created at: April 29, 2026, 6:22 p.m.