Triple
T32470196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bingham Canyon Mine |
E829827
|
entity |
| Predicate | startOfOpenPitOperations |
P163849
|
FINISHED |
| Object | 1906 |
—
|
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: 1906 | Statement: [Bingham Canyon Mine, startOfOpenPitOperations, 1906]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfOpenPitOperations Context triple: [Bingham Canyon Mine, startOfOpenPitOperations, 1906]
-
A.
modernOpenPitMiningStart
chosen
Indicates that the point in time marks the beginning of modern open-pit mining operations at a given location or for a given resource.
-
B.
hasOpenPitMine
Indicates that an entity operates, contains, or is associated with an open-pit mining site.
-
C.
openedToProspectors
Indicates that access or rights to a resource, area, or opportunity have been made available for exploration, evaluation, or exploitation by prospectors.
-
D.
pitOpeningPeriod
Indicates the time span during which a pit (such as an excavation or mining pit) is open, accessible, or in active use.
-
E.
operatedAsMineUntil
Indicates that an entity functioned in the capacity of a mine up to a specified point in time.
- 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
Created at: May 1, 2026, 12:57 a.m.