Triple
T5386649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin script (1929–1940) |
E120216
|
entity |
| Predicate | scriptChangeReason |
P6009
|
FINISHED |
| Object | Soviet language policy reforms |
—
|
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: Soviet language policy reforms | Statement: [Latin script (1929–1940), scriptChangeReason, Soviet language policy reforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptChangeReason Context triple: [Latin script (1929–1940), scriptChangeReason, Soviet language policy reforms]
-
A.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
B.
reasonForChange
chosen
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
C.
scriptChangePolicy
Indicates a policy governing when, how, or under what conditions a script may be modified or updated.
-
D.
replacedBecause
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
-
E.
nameChangeReason
Indicates the reason or justification for a change in an entity’s name.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd86f6f39c8190aa6af12370e3d12b |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.