Triple
T29544164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pike’s Peak Gold Rush |
E749584
|
entity |
| Predicate | estimatedNumberOfProspectors |
P174290
|
FINISHED |
| Object | over 100000 |
—
|
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: over 100000 | Statement: [Pike’s Peak Gold Rush, estimatedNumberOfProspectors, over 100000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedNumberOfProspectors Context triple: [Pike’s Peak Gold Rush, estimatedNumberOfProspectors, over 100000]
-
A.
openedToProspectors
Indicates that access or rights to a resource, area, or opportunity have been made available for exploration, evaluation, or exploitation by prospectors.
-
B.
numberOfMinersDepicted
Indicates the quantity of miners shown or represented in a given context.
-
C.
employsApproximateNumberOfPeople
Indicates that an entity employs a roughly estimated or approximate number of people, rather than an exact headcount.
-
D.
estimatedNumberOfBeneficiaries
Indicates the approximate count of individuals or entities expected to receive benefits from something.
-
E.
estimatedMemberCount
Indicates the approximate or predicted number of members associated with an entity.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69f6bbf5a8288190ae170bcbe8ab65cf |
completed | May 3, 2026, 3:07 a.m. |
Created at: April 28, 2026, 5:06 p.m.