Triple
T28929345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cerro Verde copper deposit |
E733737
|
entity |
| Predicate | alterationTypes |
P144621
|
FINISHED |
| Object | potassic alteration |
—
|
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: potassic alteration | Statement: [Cerro Verde copper deposit, alterationTypes, potassic alteration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alterationTypes Context triple: [Cerro Verde copper deposit, alterationTypes, potassic alteration]
-
A.
alterationType
chosen
Indicates the specific kind or category of change or modification that has been applied to an entity or relationship.
-
B.
alterationStyles
Indicates the styles, methods, or types of modifications or alterations applied to an entity.
-
C.
typeOfAmendment
Indicates the specific kind or category of amendment that is being applied to something, such as a document, law, or agreement.
-
D.
changeType
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
-
E.
hasArchitecturalModificationType
Indicates that an entity has undergone a specific type or category of architectural modification.
- 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_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 8:26 a.m.