Triple
T30771588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trona, California |
E783536
|
entity |
| Predicate | minedMineral |
P45236
|
FINISHED |
| Object | sodium carbonate |
—
|
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: sodium carbonate | Statement: [Trona, California, minedMineral, sodium carbonate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minedMineral Context triple: [Trona, California, minedMineral, sodium carbonate]
-
A.
typeOfMineralProduced
Indicates that a specified mineral is produced or extracted as a result of a particular process, operation, or source.
-
B.
isMineralRich
Indicates that a location or substance contains a high concentration or abundance of minerals.
-
C.
hasMineral
chosen
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
D.
mineName
Indicates that an entity has or is associated with a specific mine identified by a given name.
-
E.
discoveryOfOre
Indicates the event or relationship in which a particular ore deposit is found, identified, or recognized, typically linking the discoverer, the ore, and the location or time of discovery.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fc1913081909b621a90cb555115 |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:40 p.m.