Triple

T37907541
Position Surface form Disambiguated ID Type / Status
Subject Kumba Iron Ore E945595 entity
Predicate hasMiningRightFor P120263 FINISHED
Object Sishen mine NE NERFINISHED

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: Sishen mine | Statement: [Kumba Iron Ore, hasMiningRightFor, Sishen mine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMiningRightFor
Context triple: [Kumba Iron Ore, hasMiningRightFor, Sishen mine]
  • A. hasMiningLease chosen
    Indicates that one entity holds a legal right or authorization to explore for or extract minerals or other resources from land or a specific area owned or controlled by another entity.
  • B. hasMiningArea
    Indicates that an entity possesses, controls, or is associated with a designated area where mining activities take place.
  • C. hasMiningLicenseJurisdiction
    Indicates that an authority or region has legal jurisdiction over the issuance, regulation, or enforcement of a mining license.
  • D. hasMiningDeposit
    Indicates that one entity contains or is the location of a mineable natural resource deposit associated with another entity.
  • 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_69f76ef20bb0819088b5b6ceecb0b8fc completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fd864235b481908738dbb69556bc62 completed May 8, 2026, 6:44 a.m.
PD Predicate disambiguation batch_69fd8373b6bc819091c554f29ee17fec completed May 8, 2026, 6:32 a.m.
Created at: May 3, 2026, 4:20 p.m.