Triple
T31694575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terlingua |
E808883
|
entity |
| Predicate | majorCommodityMined |
P64308
|
FINISHED |
| Object | mercury |
—
|
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: mercury | Statement: [Terlingua, majorCommodityMined, mercury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCommodityMined Context triple: [Terlingua, majorCommodityMined, mercury]
-
A.
typeOfMineralProduced
Indicates that a specified mineral is produced or extracted as a result of a particular process, operation, or source.
-
B.
hasMiningCommodity
chosen
Indicates that an entity is associated with, produces, or contains a specific mining-related commodity.
-
C.
miningCompany
Indicates a relationship where an entity operates as a company engaged in the extraction of natural resources from the earth.
-
D.
allegedPrimaryCommodity
Indicates that something is claimed or reported, but not confirmed, to be the main commodity associated with an entity or activity.
-
E.
eraOfMajorMiningActivity
Indicates the time period during which significant or primary mining operations took place for the associated entity.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe9dfaa2d08190b2084f63f842eb6b |
completed | May 9, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69fe9bba947c81908b0b2b92a4d19b37 |
completed | May 9, 2026, 2:28 a.m. |
Created at: April 30, 2026, 11:09 p.m.