Triple
T30092716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korba Coalfield |
E764778
|
entity |
| Predicate | previousAdministrativeStateUntil |
P30469
|
FINISHED |
| Object | 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: 2000 | Statement: [Korba Coalfield, previousAdministrativeStateUntil, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousAdministrativeStateUntil Context triple: [Korba Coalfield, previousAdministrativeStateUntil, 2000]
-
A.
previousMunicipalityStatus
Indicates that one municipality previously held a particular municipal status or classification before a change occurred.
-
B.
formerAdministrativeStatus
Indicates that an entity previously held, but no longer holds, a particular administrative status or role.
-
C.
previousStateName
Indicates the name of the state that immediately preceded the current state in a process or state transition.
-
D.
previousAdministrator
Indicates that one entity formerly held an administrative role or position over another entity before the current administrator.
-
E.
formerState
chosen
Indicates that an entity previously held the status or condition of a particular state but no longer does so.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 29, 2026, 7:06 p.m.