Triple
T29128344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuajone copper deposit |
E738295
|
entity |
| Predicate | minedByMethod |
P10923
|
FINISHED |
| Object | truck-and-shovel open-pit operations |
—
|
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: truck-and-shovel open-pit operations | Statement: [Cuajone copper deposit, minedByMethod, truck-and-shovel open-pit operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minedByMethod Context triple: [Cuajone copper deposit, minedByMethod, truck-and-shovel open-pit operations]
-
A.
minedBy
Indicates that a resource, material, or location is extracted or obtained through mining activities performed by a specified agent or entity.
-
B.
minimizedBy
Indicates that one entity serves to reduce, lessen, or make as small as possible the value, effect, or impact of another entity.
-
C.
mainMiningMethod
Indicates the primary mining technique or process predominantly used in extracting resources at a given site or operation.
-
D.
miningMethod
chosen
Indicates the technique or process used to extract minerals or resources from the earth.
-
E.
createdByMethod
Indicates that something was produced, generated, or brought into existence through a specific method or procedure.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6622c2e1c819093b43ecb65f3fa52 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:30 a.m.