Triple
T10318715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akmola |
E242084
|
entity |
| Predicate | renamedInContextOf |
P30638
|
FINISHED |
| Object | Kazakhstan capital relocation policy |
—
|
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: Kazakhstan capital relocation policy | Statement: [Akmola, renamedInContextOf, Kazakhstan capital relocation policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamedInContextOf Context triple: [Akmola, renamedInContextOf, Kazakhstan capital relocation policy]
-
A.
contextOfRenaming
chosen
Indicates the situational or historical context in which an entity’s name was or is being changed.
-
B.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
C.
namedInContextOf
Indicates that an entity is mentioned or identified specifically within a particular context, situation, or frame of reference.
-
D.
renamedTo
Indicates that an entity has been given a new name, specifying the target name it was changed to.
-
E.
relocationContext
Indicates the circumstances, reasons, and situational details surrounding an entity’s move or transfer from one place or position to another.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f4f354819080b4ed4bc61bdff6 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:49 a.m.