Triple
T38109835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marysvale, Utah |
E951624
|
entity |
| Predicate | historicalResourceMined |
P83036
|
FINISHED |
| Object | uranium |
—
|
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: uranium | Statement: [Marysvale, Utah, historicalResourceMined, uranium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalResourceMined Context triple: [Marysvale, Utah, historicalResourceMined, uranium]
-
A.
historicallySuppliedOreTo
Indicates that one entity provided ore to another entity as a supplier during a past historical period.
-
B.
miningHeritage
Indicates a historical or cultural connection to mining activities, sites, or traditions.
-
C.
miningHistory
Indicates a historical record or past occurrence of mining-related activities or operations associated with an entity.
-
D.
wasExtensivelyMinedIn
Indicates that a location or resource was subject to intensive or large-scale mining activity during a specified time or by a specified agent.
-
E.
resourceHistoricallyExtracted
chosen
Indicates that a resource was extracted from a location or entity during some period in the past, but not necessarily in the present.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0204dafcc08190868a6f3eab162505 |
completed | May 11, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_6a0202dc60348190a140bb9da906f5b6 |
completed | May 11, 2026, 4:25 p.m. |
Created at: May 3, 2026, 4:21 p.m.