Triple
T21702955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zheleznogorsk (iron city) |
E535698
|
entity |
| Predicate | resourceTypeMined |
P115741
|
FINISHED |
| Object | iron ore |
—
|
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: iron ore | Statement: [Zheleznogorsk (iron city), resourceTypeMined, iron ore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceTypeMined Context triple: [Zheleznogorsk (iron city), resourceTypeMined, iron ore]
-
A.
hasMiningCommodity
Indicates that an entity is associated with, produces, or contains a specific mining-related commodity.
-
B.
typeOfMineralProduced
chosen
Indicates that a specified mineral is produced or extracted as a result of a particular process, operation, or source.
-
C.
minerRepresents
Indicates that a miner acts on behalf of, or serves as a representative or proxy for, another entity in a given context.
-
D.
resourceDepletionStatus
Indicates the current state or level of exhaustion of a particular resource, such as whether it is abundant, diminishing, or depleted.
-
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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b8161348190842c433531cfaa5b |
completed | April 27, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.