Triple
T2756905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jharkhand |
E61121
|
entity |
| Predicate | hasHighMineralReservesOf |
P28979
|
FINISHED |
| Object | coal |
—
|
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 | Statement: [Jharkhand, hasHighMineralReservesOf, coal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighMineralReservesOf Context triple: [Jharkhand, hasHighMineralReservesOf, coal]
-
A.
hasImportantMineral
chosen
Indicates that an entity contains or is associated with a mineral considered significant or valuable in a given context.
-
B.
hasSignificantOilReservesInRegion
Indicates that an entity possesses substantial oil reserves located within a specified geographic region.
-
C.
hasMiningDistrict
Indicates that an entity possesses, contains, or is associated with a designated mining district within its domain or jurisdiction.
-
D.
quarriedFor
Indicates that a location or source is excavated or mined in order to obtain a particular material or resource.
-
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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb8a292c8190ab3982434805241a |
completed | March 7, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69abd82d005c81908a1ac7a1313c6d88 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.