Triple
T30707250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vukovica |
E781785
|
entity |
| Predicate | hasKeyReform |
P148277
|
FINISHED |
| Object | simplification of Cyrillic alphabet |
—
|
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: simplification of Cyrillic alphabet | Statement: [Vukovica, hasKeyReform, simplification of Cyrillic alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyReform Context triple: [Vukovica, hasKeyReform, simplification of Cyrillic alphabet]
-
A.
hasKeyReformer
Indicates that an entity has a primary individual responsible for driving significant change or reform within it.
-
B.
hasKeyReformArea
chosen
Indicates that an entity is associated with or involves a primary or central area of reform.
-
C.
hasKeyReissue
Indicates that a key has been issued again to an entity, typically replacing or updating a previous key.
-
D.
hasKeyChange
Indicates that an entity undergoes or involves a change of key, such as a modulation or shift in tonal center.
-
E.
hasKeyPass
Indicates that an entity possesses or is granted a key-based pass that allows access or authorization to something.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 29, 2026, 8:35 p.m.