Triple
T33078011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumpter Valley |
E846422
|
entity |
| Predicate | miningMethodHistory |
P10923
|
FINISHED |
| Object | bucket‑line dredging |
—
|
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: bucket‑line dredging | Statement: [Sumpter Valley, miningMethodHistory, bucket‑line dredging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: miningMethodHistory Context triple: [Sumpter Valley, miningMethodHistory, bucket‑line dredging]
-
A.
miningHistory
Indicates a historical record or past occurrence of mining-related activities or operations associated with an entity.
-
B.
miningMethod
chosen
Indicates the technique or process used to extract minerals or resources from the earth.
-
C.
miningHeritage
Indicates a historical or cultural connection to mining activities, sites, or traditions.
-
D.
historicallySuppliedOreTo
Indicates that one entity provided ore to another entity as a supplier during a past historical period.
-
E.
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.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.