Triple
T25573981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andal |
E641054
|
entity |
| Predicate | coalMiningRegion |
P115090
|
FINISHED |
| Object | Damodar Valley coal mining belt |
—
|
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: Damodar Valley coal mining belt | Statement: [Andal, coalMiningRegion, Damodar Valley coal mining belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coalMiningRegion Context triple: [Andal, coalMiningRegion, Damodar Valley coal mining belt]
-
A.
isInCoalRegion
Indicates that an entity is located within a geographic region characterized by coal deposits, coal mining, or coal-related activities.
-
B.
locatedInMiningBelt
chosen
Indicates that an entity is situated within a designated mining belt or mining region.
-
C.
coalMinedFrom
Indicates that a quantity or batch of coal has been extracted from a particular source location, such as a mine or geological deposit.
-
D.
quarryRegion
Indicates that a specified region is the location where quarrying or extraction activities take place.
-
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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f92ee22c81909f1de62c9023af1b |
completed | May 2, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 4 p.m.