Triple
T29941396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio Tinto aluminum smelter |
E760507
|
entity |
| Predicate | isFacilityOf |
P168281
|
FINISHED |
| Object | Rio Tinto |
—
|
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 | Statement: [Rio Tinto aluminum smelter, isFacilityOf, Rio Tinto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFacilityOf Context triple: [Rio Tinto aluminum smelter, isFacilityOf, Rio Tinto]
-
A.
isNamedFacilityOf
Indicates that a facility bears the official name associated with a particular entity (such as an organization, person, or place).
-
B.
isPrimaryFacilityFor
Indicates that one facility serves as the main or principal location responsible for supporting or serving a particular entity or operation.
-
C.
identifiesFacility
Indicates that one entity serves to recognize, specify, or distinguish a particular facility as the relevant or associated one.
-
D.
servesFacility
Indicates that one entity provides services or support to a particular facility as its client, target, or area of operation.
-
E.
legacyFacilityOf
Indicates that one facility is an older, predecessor, or superseded version of another facility within the same organizational or operational context.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f678066d24819099ae7947cfb58743 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:22 p.m.