Triple
T6273402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver City, Nevada |
E140592
|
entity |
| Predicate | foundedDuringPeriod |
P7058
|
FINISHED |
| Object | Comstock Lode boom |
—
|
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: Comstock Lode boom | Statement: [Silver City, Nevada, foundedDuringPeriod, Comstock Lode boom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedDuringPeriod Context triple: [Silver City, Nevada, foundedDuringPeriod, Comstock Lode boom]
-
A.
foundingPeriod
chosen
Indicates the time span or historical period during which an entity (such as an organization, settlement, or institution) was founded.
-
B.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other entity.
-
C.
foundedAfter
Indicates that one entity was founded at a later time than another entity.
-
D.
flourishedDuring
Indicates that an entity was active, thriving, or at its peak during a specified time period or era.
-
E.
foundedInYearApprox
Indicates that an entity was established or came into existence around an approximate year, rather than on a precisely known date.
- 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_69c008cc158881908df6ec94a911c736 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063be5a148190a8752426d2d220f8 |
completed | March 22, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69c05606fb50819082d1a5a91e5030b6 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.