Triple
T15547342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austin, Nevada |
E370644
|
entity |
| Predicate | historicPeakPeriod |
P42593
|
FINISHED |
| Object | 1860s |
—
|
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: 1860s | Statement: [Austin, Nevada, historicPeakPeriod, 1860s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicPeakPeriod Context triple: [Austin, Nevada, historicPeakPeriod, 1860s]
-
A.
historicalPeak
Indicates that the related value or state represents the highest level ever reached by something within a historical or recorded time frame.
-
B.
populationPeakPeriod
chosen
Indicates the time period during which a population reached its highest recorded level.
-
C.
historicHighPowerEra
Indicates that the subject existed or operated during a past period characterized by especially high levels of power, influence, or capability.
-
D.
historicalPass
Indicates that an entity has successfully completed or passed a historical event, period, or examination related to history.
-
E.
historicalPeakIndustrialPeriod
Indicates the time period during which an entity reached its highest level of industrial activity or development.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a9073948190b6e9cf504aacc7cf |
completed | April 16, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:08 a.m.