Triple
T9994471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porcupine mining camp |
E196967
|
entity |
| Predicate | startOfGoldRush |
P91474
|
FINISHED |
| Object | 1910 |
—
|
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: 1910 | Statement: [Porcupine mining camp, startOfGoldRush, 1910]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfGoldRush Context triple: [Porcupine mining camp, startOfGoldRush, 1910]
-
A.
goldRushEra
Indicates a relationship or context tied to the historical period characterized by intense migration and mining activity driven by newly discovered gold.
-
B.
goldDiscovered
Indicates that an instance of gold has been found or identified at a particular time, place, or context.
-
C.
foundedAsMiningCamp
Indicates that a settlement or town was originally established as a mining camp.
-
D.
firstCommercialMiningStartedBy
Indicates that the referenced entity initiated the first commercial mining operations on the associated resource, site, or deposit.
-
E.
roleInGoldRush
Indicates that an entity played a specific role or had a particular involvement in the historical event known as the Gold Rush.
- F. None of above. chosen
Provenance (4 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcb982d5c81909779c6e9d780b399 |
completed | April 2, 2026, 1:51 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:50 p.m.