Triple
T30993841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lead, South Dakota |
E789738
|
entity |
| Predicate | HomestakeMineOperatedFrom |
P152124
|
FINISHED |
| Object | late 19th century to early 21st century |
—
|
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: late 19th century to early 21st century | Statement: [Lead, South Dakota, HomestakeMineOperatedFrom, late 19th century to early 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HomestakeMineOperatedFrom Context triple: [Lead, South Dakota, HomestakeMineOperatedFrom, late 19th century to early 21st century]
-
A.
minesOperatedBy
Indicates that a mine is operated or run by a particular organization or entity.
-
B.
foundedAsMiningTownIn
Indicates that a settlement or town was originally established as a mining town in the specified location or jurisdiction.
-
C.
foundedAsMiningCamp
Indicates that a settlement or town was originally established as a mining camp.
-
D.
operatedAsMineUntil
chosen
Indicates that an entity functioned in the capacity of a mine up to a specified point in time.
-
E.
miningSite
Indicates a location where mining activities or mineral extraction operations take place.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:56 p.m.