Triple
T13578736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capps Mine |
E324353
|
entity |
| Predicate | hasTypeOfOreDeposit |
P110138
|
FINISHED |
| Object | lode gold deposit (general type) |
—
|
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: lode gold deposit (general type) | Statement: [Capps Mine, hasTypeOfOreDeposit, lode gold deposit (general type)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfOreDeposit Context triple: [Capps Mine, hasTypeOfOreDeposit, lode gold deposit (general type)]
-
A.
hasMiningCommodity
Indicates that an entity is associated with, produces, or contains a specific mining-related commodity.
-
B.
hasMineral
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
C.
hasOpenPitMine
Indicates that an entity operates, contains, or is associated with an open-pit mining site.
-
D.
hasGeologicResource
Indicates that an entity possesses, contains, or is associated with a particular geologic resource.
-
E.
hasImportantMineral
Indicates that an entity contains or is associated with a mineral considered significant or valuable in a given context.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb03052088190a2b68c106059828e |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaf7fefa881908471f1400f813ccc |
completed | April 12, 2026, 2:43 p.m. |
Created at: April 9, 2026, 9:48 p.m.