Triple
T27754462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San José copper–gold mine |
E701300
|
entity |
| Predicate | typeOfOreBody |
P110138
|
FINISHED |
| Object | copper–gold deposit |
—
|
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: copper–gold deposit | Statement: [San José copper–gold mine, typeOfOreBody, copper–gold deposit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfOreBody Context triple: [San José copper–gold mine, typeOfOreBody, copper–gold deposit]
-
A.
primaryOreBody
Indicates that an ore body is the main or most significant source of mineralization within a given deposit or mining project.
-
B.
hasTypeOfOreDeposit
chosen
Indicates that an entity possesses or is associated with a specific type of ore deposit.
-
C.
typeOfMineralProduced
Indicates that a specified mineral is produced or extracted as a result of a particular process, operation, or source.
-
D.
primaryOreTypes
Indicates the main types of ore that are predominantly associated with or extracted from a given entity.
-
E.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 27, 2026, 4:22 p.m.