Triple
T27098261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Sandy River |
E686367
|
entity |
| Predicate | economicActivityInBasin |
P114644
|
FINISHED |
| Object | coal 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: coal mining | Statement: [Big Sandy River, economicActivityInBasin, coal mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicActivityInBasin Context triple: [Big Sandy River, economicActivityInBasin, coal mining]
-
A.
regionalEconomyActivity
chosen
Indicates the type or level of economic activity occurring within a specific geographic region.
-
B.
regionalEconomyType
Indicates the type or classification of an economy associated with a specific region.
-
C.
economicSectorDominant
Indicates that one economic sector holds a leading or controlling position relative to others in terms of influence, output, or importance.
-
D.
economicSectorSourceOfWealth
Indicates that a particular economic sector is the primary source from which an entity derives its wealth or income.
-
E.
basinPopulationActivity
Indicates the level or type of human activity occurring within the population of a drainage basin or watershed area.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 8:46 a.m.