Triple
T21832220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amrun Mine |
E539024
|
entity |
| Predicate | hasOwnerStake |
P99020
|
FINISHED |
| Object | Rio Tinto majority interest |
—
|
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: Rio Tinto majority interest | Statement: [Amrun Mine, hasOwnerStake, Rio Tinto majority interest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOwnerStake Context triple: [Amrun Mine, hasOwnerStake, Rio Tinto majority interest]
-
A.
hasStake
Indicates that one entity holds an interest, share, or involvement—financial, strategic, or otherwise—in another entity or outcome.
-
B.
ownershipStake
chosen
Indicates that one entity holds a partial or full ownership interest or equity stake in another entity.
-
C.
hasOwnerShare
Indicates that an entity holds a specified ownership stake or share in another entity or asset.
-
D.
hasCapitalOwnerRole
Indicates that an entity holds the role or status of owning capital in relation to another entity or asset.
-
E.
hasVotingStake
Indicates that one entity possesses a share of voting power or decision-making authority in another entity.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7a4d2d0819088ded045caeab52d |
completed | April 28, 2026, 12:27 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.