Triple
T31806374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tole Bi District |
E811883
|
entity |
| Predicate | formerRegionName |
P171724
|
FINISHED |
| Object | South Kazakhstan Region |
—
|
NE NERFINISHED |
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: South Kazakhstan Region | Statement: [Tole Bi District, formerRegionName, South Kazakhstan Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerRegionName Context triple: [Tole Bi District, formerRegionName, South Kazakhstan Region]
-
A.
formerNameOfRegion
chosen
Indicates that one name was previously used for a region that is now known by a different name.
-
B.
formerRegionBefore2016
Indicates that an entity was recognized as a region prior to the year 2016 but no longer holds that regional status after 2016.
-
C.
formerServesRegion
Indicates that an entity previously served, represented, or had official responsibility for a given region, but no longer does so.
-
D.
formerNameOfAreaWithin
Indicates that one area previously had a different name while remaining within the same larger encompassing area.
-
E.
formerAdministrativeTerritory
Indicates that one entity was previously an official administrative territory of another entity but no longer holds that status.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: April 30, 2026, 11:42 p.m.