Triple
T17447813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazakhstan |
E424829
|
entity |
| Predicate | plannedScriptChangeTo |
P36091
|
FINISHED |
| Object | Latin script |
—
|
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: Latin script | Statement: [Kazakhstan, plannedScriptChangeTo, Latin script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedScriptChangeTo Context triple: [Kazakhstan, plannedScriptChangeTo, Latin script]
-
A.
plannedUpgrade
Indicates that an entity has a scheduled or intended improvement or enhancement to be carried out in the future.
-
B.
namespaceChangedTo
Indicates that an entity’s namespace has been updated or reassigned from its previous value to a new one.
-
C.
scriptUsageChange
Indicates a change in how a script is used, such as modifications to its invocation, parameters, frequency, or execution context over time.
-
D.
plannedAdaptation
Indicates that an adaptation or modification has been intentionally designed or scheduled to occur in response to certain conditions or goals.
-
E.
plannedReplacement
chosen
Indicates that one entity is intended or scheduled to be replaced by another entity in the future.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ffe18f08190be023de89e3d7d5c |
completed | April 19, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.