Triple
T16664188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eureka Mining District |
E404936
|
entity |
| Predicate | primaryOreType |
P64309
|
FINISHED |
| Object | silver‑lead ore |
—
|
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: silver‑lead ore | Statement: [Eureka Mining District, primaryOreType, silver‑lead ore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOreType Context triple: [Eureka Mining District, primaryOreType, silver‑lead ore]
-
A.
primaryOreTypes
chosen
Indicates the main types of ore that are predominantly associated with or extracted from a given entity.
-
B.
primaryOreBody
Indicates that an ore body is the main or most significant source of mineralization within a given deposit or mining project.
-
C.
typeOfMineralProduced
Indicates that a specified mineral is produced or extracted as a result of a particular process, operation, or source.
-
D.
primaryExtraction
Indicates that an entity is the main or initial source from which another entity, resource, or substance is obtained or derived.
-
E.
primaryType
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9afd048190b73bbc9c423915ca |
completed | April 18, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.