Triple
T33331422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Bloomfield |
E853416
|
entity |
| Predicate | usedMiningMethod |
P10923
|
FINISHED |
| Object | hydraulic 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: hydraulic mining | Statement: [North Bloomfield, usedMiningMethod, hydraulic mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedMiningMethod Context triple: [North Bloomfield, usedMiningMethod, hydraulic mining]
-
A.
miningMethod
chosen
Indicates the technique or process used to extract minerals or resources from the earth.
-
B.
mainMiningMethod
Indicates the primary mining technique or process predominantly used in extracting resources at a given site or operation.
-
C.
wasExtensivelyMinedIn
Indicates that a location or resource was subject to intensive or large-scale mining activity during a specified time or by a specified agent.
-
D.
isMinedIn
Indicates that a resource or material is extracted or obtained from a particular location or site.
-
E.
miningScale
Indicates the relative size or intensity of a mining operation or activity.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.