Triple
T34472477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keweenaw copper mining district |
E884941
|
entity |
| Predicate | startOfLargeScaleIndustrialMining |
P156639
|
FINISHED |
| Object | 1840s |
—
|
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: 1840s | Statement: [Keweenaw copper mining district, startOfLargeScaleIndustrialMining, 1840s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfLargeScaleIndustrialMining Context triple: [Keweenaw copper mining district, startOfLargeScaleIndustrialMining, 1840s]
-
A.
startOfIndustrialMining
chosen
Indicates the point in time when industrial-scale mining activities begin at a given location or for a given resource.
-
B.
eraOfMajorMiningActivity
Indicates the time period during which significant or primary mining operations took place for the associated entity.
-
C.
declineOfLargeScaleMining
Indicates a reduction or downturn in the extent, intensity, or prevalence of large-scale mining activities.
-
D.
historicalPeriodOfIndustrialUse
Indicates the historical time span during which an entity was used for industrial purposes.
-
E.
miningScale
Indicates the relative size or intensity of a mining operation or activity.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00372ff0e48190b3ed91f9bae9da6c |
completed | May 10, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_6a00359c1b8481909c1e43df9f5a789a |
completed | May 10, 2026, 7:37 a.m. |
Created at: May 1, 2026, 2:01 a.m.