Triple
T12196168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barrier Ranges |
E290589
|
entity |
| Predicate | hasMiningType |
P44639
|
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: [Barrier Ranges, hasMiningType, hard rock mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiningType Context triple: [Barrier Ranges, hasMiningType, hard rock mining]
-
A.
hasMiningCommodity
Indicates that an entity is associated with, produces, or contains a specific mining-related commodity.
-
B.
hasMiningActivity
Indicates that some form of mining operation or extraction activity is occurring at, involving, or associated with the referenced entity.
-
C.
hasMiningArea
Indicates that an entity possesses, controls, or is associated with a designated area where mining activities take place.
-
D.
hasMineType
chosen
Indicates that an entity is associated with or characterized by a specific type or category of mine.
-
E.
hasMiningProject
Indicates that an entity is associated with, operates, or is responsible for a mining project.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:50 p.m.