Triple
T32322024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hodbarrow iron ore mines |
E825798
|
entity |
| Predicate | minedProduct |
P64308
|
FINISHED |
| Object | hematite |
—
|
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: hematite | Statement: [Hodbarrow iron ore mines, minedProduct, hematite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minedProduct Context triple: [Hodbarrow iron ore mines, minedProduct, hematite]
-
A.
typeOfMineralProduced
Indicates that a specified mineral is produced or extracted as a result of a particular process, operation, or source.
-
B.
hasMiningCommodity
chosen
Indicates that an entity is associated with, produces, or contains a specific mining-related commodity.
-
C.
mineName
Indicates that an entity has or is associated with a specific mine identified by a given name.
-
D.
minerRepresents
Indicates that a miner acts on behalf of, or serves as a representative or proxy for, another entity in a given context.
-
E.
miningMethod
Indicates the technique or process used to extract minerals or resources from the earth.
- 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bde419a48190b76643481d078c4e |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:47 a.m.