Triple
T21495289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Candelaria mining district |
E530335
|
entity |
| Predicate | otherCommodity |
P144620
|
FINISHED |
| Object | gold |
—
|
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: gold | Statement: [Candelaria mining district, otherCommodity, gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherCommodity Context triple: [Candelaria mining district, otherCommodity, gold]
-
A.
commodity
Indicates that one entity is a tradable good or resource that is bought, sold, or exchanged in relation to another entity.
-
B.
commodityType
Indicates the classification of a good or product according to its type or category within a commodity system.
-
C.
commodityClass
Indicates that one entity is classified as belonging to a particular category or class of commodities in relation to another entity.
-
D.
commodityProduced
Indicates that a particular commodity is generated, manufactured, or otherwise produced by a specified entity or process.
-
E.
mentionsCommodity
Indicates that one entity refers to, cites, or brings up a particular commodity in some form of content or communication.
- F. None of above. chosen
Provenance (4 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea575f2c81909cc0607c4b529f8d |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:23 p.m.