Triple
T29006222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toquepala copper deposit |
E736440
|
entity |
| Predicate | depositTypeModel |
P109495
|
FINISHED |
| Object | Andean-type 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: Andean-type porphyry copper system | Statement: [Toquepala copper deposit, depositTypeModel, Andean-type porphyry copper system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depositTypeModel Context triple: [Toquepala copper deposit, depositTypeModel, Andean-type porphyry copper system]
-
A.
depositType
Indicates the specific kind or category of deposit associated with an account, transaction, or financial arrangement.
-
B.
oreDepositType
chosen
Indicates the specific classification of an ore deposit based on how it formed or its characteristic geological features.
-
C.
depositTypeRecognized
Indicates that the type of deposit involved in a transaction or context has been identified and classified as a valid, known category.
-
D.
hasDepositType
Indicates that an entity is associated with or classified by a particular type of deposit.
-
E.
typeOfDeposits
Indicates the specific kinds or categories of deposits associated with an account, entity, or transaction.
- 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_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. |
Created at: April 28, 2026, 9:38 a.m.