Triple
T7306600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jharia coalfield |
E167988
|
entity |
| Predicate | hasLongstanding |
P71432
|
FINISHED |
| Object | uncontrolled coal seam fires |
—
|
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: uncontrolled coal seam fires | Statement: [Jharia coalfield, hasLongstanding, uncontrolled coal seam fires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLongstanding Context triple: [Jharia coalfield, hasLongstanding, uncontrolled coal seam fires]
-
A.
isLongStanding
Indicates that a relationship, condition, or state has existed for a considerable or extended period of time.
-
B.
hasLongHistory
chosen
Indicates that the relationship or subject has existed or persisted over a long period of time.
-
C.
hasPermanentSeniority
Indicates that one entity holds a fixed, enduring precedence or higher rank over another that does not change over time.
-
D.
establishedFollowing
Indicates that one entity created or set up another entity after, and in consequence of, a prior entity or event.
-
E.
hasHistoryOf
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebd7dcf88190b3e66bea327fc63d |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.