Triple
T28929356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cerro Verde copper deposit |
E733737
|
entity |
| Predicate | mineralSystem |
P27396
|
FINISHED |
| Object | porphyry copper system |
—
|
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: porphyry copper system | Statement: [Cerro Verde copper deposit, mineralSystem, porphyry copper system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mineralSystem Context triple: [Cerro Verde copper deposit, mineralSystem, porphyry copper system]
-
A.
hasMineralFeature
Indicates that one entity possesses, contains, or is characterized by a specific mineral-related feature or attribute.
-
B.
geologicalSystem
chosen
Indicates that one entity is a geological system (e.g., rock units, structures, or processes forming a coherent geologic framework) associated with or characterizing the other entity.
-
C.
mineralGroup
Indicates that one entity is classified as a member or subtype of a particular mineral group defined by shared mineralogical characteristics.
-
D.
isMineralRich
Indicates that a location or substance contains a high concentration or abundance of minerals.
-
E.
hasMineral
Indicates that one entity contains, includes, or is composed of a specified mineral.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65b51b63c8190aa4f80f17f587aeb |
completed | May 2, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:26 a.m.