Triple
T27372533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raniganj |
E690364
|
entity |
| Predicate | locatedInCoalfield |
P107533
|
FINISHED |
| Object | Raniganj 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: Raniganj coalfield | Statement: [Raniganj, locatedInCoalfield, Raniganj coalfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCoalfield Context triple: [Raniganj, locatedInCoalfield, Raniganj coalfield]
-
A.
isInCoalRegion
Indicates that an entity is located within a geographic region characterized by coal deposits, coal mining, or coal-related activities.
-
B.
locatedInHistoricMiningTown
Indicates that something is situated within a town historically associated with mining activity.
-
C.
associatedWithCoalfield
chosen
Indicates a relationship in which something is connected or linked to a particular coalfield, such as by location, operation, ownership, or relevance.
-
D.
locatedInFormerMiningArea
Indicates that an entity is situated within an area that was previously used for mining activities.
-
E.
locatedInMiningDistrict
Indicates that one entity is situated within the geographic or administrative boundaries of a specified mining district.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: April 27, 2026, 12:19 p.m.