Triple
T26223853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bharat Coking Coal Limited |
E655835
|
entity |
| Predicate | operatesInCoalfield |
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: [Bharat Coking Coal Limited, operatesInCoalfield, Jharia coalfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInCoalfield Context triple: [Bharat Coking Coal Limited, operatesInCoalfield, 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.
hasCoalMiningCompany
Indicates that an entity is associated with or owns a company whose primary business is coal mining.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 26, 2026, 8:57 p.m.