Triple
T20659015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonanza, Colorado |
E507705
|
entity |
| Predicate | economyHistoric |
P10778
|
FINISHED |
| Object | 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: mining | Statement: [Bonanza, Colorado, economyHistoric, mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economyHistoric Context triple: [Bonanza, Colorado, economyHistoric, mining]
-
A.
historicalEconomicBase
chosen
Indicates the primary type of economic activity or production that historically underpinned or sustained an entity’s economy.
-
B.
currencyHistorically
Indicates that one entity has served as the official or commonly used currency of another entity during some period in the past.
-
C.
economicTrend
Indicates the general direction or pattern of economic activity or conditions over a period of time.
-
D.
economicDataSource
Indicates the source or origin from which economic data or statistics are obtained or derived.
-
E.
economicView
Indicates a relationship where one entity holds or expresses a particular economic belief, stance, or perspective regarding economic systems, policies, or issues.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2eefd5c8190a71d4be690a6ae0e |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.