Triple
T16664187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eureka Mining District |
E404936
|
entity |
| Predicate | eraOfPeakProduction |
P3804
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Eureka Mining District, eraOfPeakProduction, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfPeakProduction Context triple: [Eureka Mining District, eraOfPeakProduction, late 19th century]
-
A.
peakYear
Indicates the year in which something reached its highest or most significant level, performance, or prominence.
-
B.
historicalPeakIndustrialPeriod
chosen
Indicates the time period during which an entity reached its highest level of industrial activity or development.
-
C.
historicalPeriodOfGreatestUse
Indicates the time period during which something was used most intensively or prevalently.
-
D.
reachedPeakInCentury
Indicates that something attained its highest level, influence, or development during a specified century.
-
E.
populationAtPeak
Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9afd048190b73bbc9c423915ca |
completed | April 18, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.