Triple
T7306591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jharia coalfield |
E167988
|
entity |
| Predicate | inStateSince |
P76121
|
FINISHED |
| Object | formation of Jharkhand in 2000 |
—
|
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: formation of Jharkhand in 2000 | Statement: [Jharia coalfield, inStateSince, formation of Jharkhand in 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inStateSince Context triple: [Jharia coalfield, inStateSince, formation of Jharkhand in 2000]
-
A.
inState
Indicates that an entity is currently located within or belongs to a particular state or condition.
-
B.
inForceSince
Indicates that a rule, law, agreement, or condition has been officially in effect starting from a specified date or time.
-
C.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
-
D.
controlledSince
Indicates that one entity has held control or authority over another entity starting from a specified point in time.
-
E.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69c6eb2d4c0c8190b4cc6fdfdb7f4827 |
completed | March 27, 2026, 8:40 p.m. |
Created at: March 27, 2026, 3:01 p.m.