Triple
T5504499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bodie State Historic Park |
E144406
|
entity |
| Predicate | goldDiscoveryYear |
P62321
|
FINISHED |
| Object | 1859 |
—
|
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: 1859 | Statement: [Bodie State Historic Park, goldDiscoveryYear, 1859]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goldDiscoveryYear Context triple: [Bodie State Historic Park, goldDiscoveryYear, 1859]
-
A.
goldDiscovered
chosen
Indicates that an instance of gold has been found or identified at a particular time, place, or context.
-
B.
goldRushEra
Indicates a relationship or context tied to the historical period characterized by intense migration and mining activity driven by newly discovered gold.
-
C.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
D.
yearOfEuropeanExploration
Indicates the specific year in which a European exploration of the referenced entity took place.
-
E.
smallestGoldDenominationAtIntroduction
Indicates the smallest value of a gold currency unit that was in circulation at the time a particular currency or monetary system was first introduced.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f0d21848190ae8c41561eca6342 |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:32 p.m.