Triple
T2197283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota Iron Company |
E50404
|
entity |
| Predicate | hasMiningOperationType |
P19172
|
FINISHED |
| Object | iron ore 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: iron ore mining | Statement: [Minnesota Iron Company, hasMiningOperationType, iron ore mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiningOperationType Context triple: [Minnesota Iron Company, hasMiningOperationType, iron ore mining]
-
A.
hasOperationType
Indicates the specific kind or category of operation associated with an entity or process.
-
B.
hasMiningActivity
chosen
Indicates that some form of mining operation or extraction activity is occurring at, involving, or associated with the referenced entity.
-
C.
miningMethod
Indicates the technique or process used to extract minerals or resources from the earth.
-
D.
hasActivityType
Indicates the specific kind or category of activity associated with an entity or event.
-
E.
hasMiningDistrict
Indicates that an entity possesses, contains, or is associated with a designated mining district within its domain or jurisdiction.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbf79f3e08190b56e9d7c0ff27237 |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.