Triple
T773672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tioga Mine |
E16338
|
entity |
| Predicate | miningType |
P10923
|
FINISHED |
| Object | hard rock 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: hard rock mining | Statement: [Tioga Mine, miningType, hard rock mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: miningType Context triple: [Tioga Mine, miningType, hard rock 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.
hasMiningDistrict
Indicates that an entity possesses, contains, or is associated with a designated mining district within its domain or jurisdiction.
-
D.
minedSince
Indicates that a resource or material has been extracted from a location continuously starting from a specified point in time.
-
E.
miningActivityEnd
Indicates the point in time or event at which a mining operation or activity ceases or is formally concluded.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a73058e481908e067b7b7f9a91cd |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a508c42c8190850a0ac7844a3ea9 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.