Triple
T28161675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia City, Montana |
E714912
|
entity |
| Predicate | discoveredGoldAt |
P62321
|
FINISHED |
| Object | Alder Gulch |
—
|
NE NERFINISHED |
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: Alder Gulch | Statement: [Virginia City, Montana, discoveredGoldAt, Alder Gulch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredGoldAt Context triple: [Virginia City, Montana, discoveredGoldAt, Alder Gulch]
-
A.
goldDiscovered
chosen
Indicates that an instance of gold has been found or identified at a particular time, place, or context.
-
B.
discoveryOfOre
Indicates the event or relationship in which a particular ore deposit is found, identified, or recognized, typically linking the discoverer, the ore, and the location or time of discovery.
-
C.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
D.
goldMineRepresents
Indicates that one entity serves as a symbolic or functional representation of a gold mine for another entity.
-
E.
treasureOwnedBy
Indicates that a particular treasure is possessed or legally held by a specific owner.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 10:06 p.m.