Triple
T36885420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telfer gold mine |
E911594
|
entity |
| Predicate | commodityCode |
P8090
|
FINISHED |
| Object | Au |
—
|
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: Au | Statement: [Telfer gold mine, commodityCode, Au]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commodityCode Context triple: [Telfer gold mine, commodityCode, Au]
-
A.
commodityType
Indicates the classification of a good or product according to its type or category within a commodity system.
-
B.
commodityClass
Indicates that one entity is classified as belonging to a particular category or class of commodities in relation to another entity.
-
C.
importedCommodity
Indicates that a commodity has been brought into a country or region from abroad through import activities.
-
D.
commodityContext
Indicates the contextual relationship in which a commodity is used, traded, or referenced (such as its market, application, or situational setting).
-
E.
catalogCode
chosen
Indicates that an entity is assigned a specific catalog identifier or code used for classification or reference.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.