Triple
T13578737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capps Mine |
E324353
|
entity |
| Predicate | geologicalResourceType |
P68054
|
FINISHED |
| Object | precious metal 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: precious metal deposit | Statement: [Capps Mine, geologicalResourceType, precious metal deposit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicalResourceType Context triple: [Capps Mine, geologicalResourceType, precious metal deposit]
-
A.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
-
B.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
C.
hasGeologicResource
chosen
Indicates that an entity possesses, contains, or is associated with a particular geologic resource.
-
D.
hasGeologicalNature
Indicates that something possesses a specific geological character, composition, or formation type.
-
E.
geologicalStatus
Indicates the current geological condition or classification of an entity, such as its formation state, activity level, or structural status within the Earth’s crust.
- 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_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. |
Created at: April 9, 2026, 9:48 p.m.