Triple
T27314553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eldorado Creek |
E689303
|
entity |
| Predicate | discoveredGoldIn |
P147997
|
FINISHED |
| Object | 1896 |
—
|
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: 1896 | Statement: [Eldorado Creek, discoveredGoldIn, 1896]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredGoldIn Context triple: [Eldorado Creek, discoveredGoldIn, 1896]
-
A.
goldDiscovered
Indicates that an instance of gold has been found or identified at a particular time, place, or context.
-
B.
discoveryOfOre
chosen
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.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
D.
goldMineRepresents
Indicates that one entity serves as a symbolic or functional representation of a gold mine for another entity.
-
E.
discoveredWith
Indicates that one entity was found, detected, or identified using another entity as the means, tool, method, or accompanying context of discovery.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 11:29 a.m.