Triple

T29493960
Position Surface form Disambiguated ID Type / Status
Subject Logan, West Virginia E748164 entity
Predicate locatedInCoalRegion P45552 FINISHED
Object coal-rich Appalachian region 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: coal-rich Appalachian region | Statement: [Logan, West Virginia, locatedInCoalRegion, coal-rich Appalachian region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInCoalRegion
Context triple: [Logan, West Virginia, locatedInCoalRegion, coal-rich Appalachian region]
  • A. isInCoalRegion chosen
    Indicates that an entity is located within a geographic region characterized by coal deposits, coal mining, or coal-related activities.
  • B. hasCoalMineNearby
    Indicates that a location or entity is situated close to at least one coal mine.
  • C. majorCoalField
    Indicates that a location is recognized as a principal or highly significant coal-producing field within a region or country.
  • D. coalMinedFrom
    Indicates that a quantity or batch of coal has been extracted from a particular source location, such as a mine or geological deposit.
  • 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_69f0bd448c6881908aa6b475cefd5ddc completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_6a0031ed5d708190ab93516ad081ada6 completed May 10, 2026, 7:21 a.m.
PD Predicate disambiguation batch_6a0031b5dbd081908eb0f4dbb8a0eac3 completed May 10, 2026, 7:20 a.m.
Created at: April 28, 2026, 4:17 p.m.