Triple

T34130391
Position Surface form Disambiguated ID Type / Status
Subject Dhanbad railway division E875406 entity
Predicate isPartOfCoalfieldRegion P107533 FINISHED
Object Jharia coalfield 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: Jharia coalfield | Statement: [Dhanbad railway division, isPartOfCoalfieldRegion, Jharia coalfield]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isPartOfCoalfieldRegion
Context triple: [Dhanbad railway division, isPartOfCoalfieldRegion, Jharia coalfield]
  • A. isInCoalRegion
    Indicates that an entity is located within a geographic region characterized by coal deposits, coal mining, or coal-related activities.
  • B. associatedWithCoalfield chosen
    Indicates a relationship in which something is connected or linked to a particular coalfield, such as by location, operation, ownership, or relevance.
  • C. majorCoalField
    Indicates that a location is recognized as a principal or highly significant coal-producing field within a region or country.
  • D. hasCoalMineNearby
    Indicates that a location or entity is situated close to at least one coal mine.
  • E. hasCoalBasin
    Indicates that one entity contains, includes, or is characterized by a coal-bearing geological basin associated with the other entity.
  • 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_69f349aa33848190a2e6c5e4533c8444 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ff409ff5548190849c2d50e99bd807 completed May 9, 2026, 2:11 p.m.
PD Predicate disambiguation batch_69ff401a5e188190a72f945e910b4a6c completed May 9, 2026, 2:09 p.m.
Created at: May 1, 2026, 1:53 a.m.