Triple
T17498755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonanza Creek |
E426139
|
entity |
| Predicate | rushPeakYears |
P60905
|
FINISHED |
| Object | 1897–1899 |
—
|
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: 1897–1899 | Statement: [Bonanza Creek, rushPeakYears, 1897–1899]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rushPeakYears Context triple: [Bonanza Creek, rushPeakYears, 1897–1899]
-
A.
peakYear
Indicates the year in which something reached its highest or most significant level, performance, or prominence.
-
B.
activeYearsPeak
chosen
Indicates the span of years during which an entity was at the height of its activity or prominence.
-
C.
membershipPeakYear
Indicates the year in which an entity’s membership count reached its highest level.
-
D.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
E.
historicalPeak
Indicates that the related value or state represents the highest level ever reached by something within a historical or recorded time frame.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4521028048190aa7c4023a72a12f4 |
completed | April 19, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.