Triple
T17446956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leadville mining district |
E424810
|
entity |
| Predicate | oreMineral |
P45236
|
FINISHED |
| Object | galena |
—
|
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: galena | Statement: [Leadville mining district, oreMineral, galena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oreMineral Context triple: [Leadville mining district, oreMineral, galena]
-
A.
hasMineral
chosen
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
B.
hasMineralFeature
Indicates that one entity possesses, contains, or is characterized by a specific mineral-related feature or attribute.
-
C.
mineralGroup
Indicates that one entity is classified as a member or subtype of a particular mineral group defined by shared mineralogical characteristics.
-
D.
typeOfMineralProduced
Indicates that a specified mineral is produced or extracted as a result of a particular process, operation, or source.
-
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.
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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ffc89e4819096372cc55b40cc3b |
completed | April 19, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.