Triple
T36885422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telfer gold mine |
E911594
|
entity |
| Predicate | hasOreBodyType |
P110138
|
FINISHED |
| Object | porphyry-style deposit |
—
|
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-style deposit | Statement: [Telfer gold mine, hasOreBodyType, porphyry-style deposit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOreBodyType Context triple: [Telfer gold mine, hasOreBodyType, porphyry-style deposit]
-
A.
hasTypeOfOreDeposit
chosen
Indicates that an entity possesses or is associated with a specific type of ore deposit.
-
B.
primaryOreBody
Indicates that an ore body is the main or most significant source of mineralization within a given deposit or mining project.
-
C.
hasMineralClass
Indicates that an entity is associated with, or categorized under, a particular mineral classification.
-
D.
hasQuarryType
Indicates that an entity functions as or is associated with a quarry of a specified type.
-
E.
hasBodyPlanType
Indicates that an organism possesses a particular overall structural or morphological body plan type.
- 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_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
Created at: May 3, 2026, 4:13 p.m.