Triple
T26135391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamuria |
E659363
|
entity |
| Predicate | coalMiningHistory |
P23360
|
FINISHED |
| Object | part of one of the oldest coalfields in India |
—
|
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: part of one of the oldest coalfields in India | Statement: [Jamuria, coalMiningHistory, part of one of the oldest coalfields in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coalMiningHistory Context triple: [Jamuria, coalMiningHistory, part of one of the oldest coalfields in India]
-
A.
hasCoalMiningHistory
chosen
Indicates that an entity has a past or ongoing involvement in coal mining activities or industry.
-
B.
miningHeritage
Indicates a historical or cultural connection to mining activities, sites, or traditions.
-
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.
collieryNow
Indicates that an entity currently functions as, or is used as, a colliery (a coal mine or mining site) at the present time.
-
E.
startOfIndustrialMining
Indicates the point in time when industrial-scale mining activities begin at a given location or for a given resource.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60b96c1ac8190adc0ceb44507777e |
completed | May 2, 2026, 2:35 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:17 p.m.