Triple
T22471524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherry Creek mining district |
E555512
|
entity |
| Predicate | significantBoomPeriod |
P65127
|
FINISHED |
| Object | 1870s |
—
|
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: 1870s | Statement: [Cherry Creek mining district, significantBoomPeriod, 1870s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantBoomPeriod Context triple: [Cherry Creek mining district, significantBoomPeriod, 1870s]
-
A.
boomPeriod
chosen
Indicates a time span during which rapid growth, expansion, or prosperity occurs in the related activity, market, or entity.
-
B.
notablePopularityPeriod
Indicates the time span during which something was especially popular or widely recognized.
-
C.
historicalPeriodOfRapidDevelopment
Indicates a time span during which something undergoes unusually fast or intense growth, change, or advancement compared to other periods.
-
D.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
E.
decadeOfPopularization
Indicates the decade during which something became widely known, used, or popular.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be0d3c08190851537660cda619c |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.