Triple
T298263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia Gold Rush |
E6140
|
entity |
| Predicate | mainMiningMethod |
P10926
|
FINISHED |
| Object | placer mining |
—
|
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: placer mining | Statement: [Georgia Gold Rush, mainMiningMethod, placer mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainMiningMethod Context triple: [Georgia Gold Rush, mainMiningMethod, placer mining]
-
A.
consensusMechanism
Indicates the method or protocol by which multiple participants in a distributed system agree on a single, consistent state or outcome.
-
B.
minedBy
Indicates that a resource, material, or location is extracted or obtained through mining activities performed by a specified agent or entity.
-
C.
mainPhase
Indicates that an event, action, or state occurs during the primary or central phase of a larger process or sequence.
-
D.
hasMiningDistrict
Indicates that an entity possesses, contains, or is associated with a designated mining district within its domain or jurisdiction.
-
E.
genesisBlockHash
Indicates the hash value that uniquely identifies the genesis (first) block of a blockchain or ledger.
- F. None of above. chosen
Provenance (4 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea4778cc8190be7b648a82542891 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e937af888190a0960708f09ae033 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea4545608190898436c72e10f39d |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.