Triple
T29006229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toquepala copper deposit |
E736440
|
entity |
| Predicate | isExploitedFor |
P165891
|
FINISHED |
| Object | metallic copper production |
—
|
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: metallic copper production | Statement: [Toquepala copper deposit, isExploitedFor, metallic copper production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExploitedFor Context triple: [Toquepala copper deposit, isExploitedFor, metallic copper production]
-
A.
exploitedFor
Indicates that one entity is unfairly or abusively used by another entity as a resource, means, or advantage for the latter’s benefit.
-
B.
exploitationPossible
Indicates that one entity is in a position to unfairly use or benefit from another entity or resource, suggesting that exploitation can occur.
-
C.
exploits
Indicates that one entity unfairly or selfishly uses another entity or resource for its own advantage or benefit.
-
D.
эксплуатируется
Indicates that one entity is being used or operated by another, often in a way that takes advantage of its resources, capabilities, or labor.
-
E.
exploitationBegan
Indicates the point in time when the exploitation or use of a resource, person, or system was initiated.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fc08c78819086abfcb2c02af163 |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65ad638ac8190a17bb987fce53279 |
completed | May 2, 2026, 8:13 p.m. |
Created at: April 28, 2026, 9:38 a.m.