Triple
T7532041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cripple Creek, Colorado |
E178046
|
entity |
| Predicate | peakGoldRushPeriod |
P55101
|
FINISHED |
| Object | 1890s |
—
|
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: 1890s | Statement: [Cripple Creek, Colorado, peakGoldRushPeriod, 1890s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakGoldRushPeriod Context triple: [Cripple Creek, Colorado, peakGoldRushPeriod, 1890s]
-
A.
goldRushEra
chosen
Indicates a relationship or context tied to the historical period characterized by intense migration and mining activity driven by newly discovered gold.
-
B.
peakServicePeriod
Indicates the time interval during which a service experiences its highest or most intensive level of use or operation.
-
C.
GoldenGenerationPeakPeriod
Indicates the time span during which a particularly talented or successful generation of a group (such as a team or cohort) reaches its highest collective performance or influence.
-
D.
peakDays
Indicates the days on which something reaches its highest or most intense level of activity, usage, or occurrence.
-
E.
launchPeriod
Indicates the time span during which a launch or deployment activity occurs or is valid.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f84753fc81908bee2013004ef5fb |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.