Triple
T31217654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valerii |
E795914
|
entity |
| Predicate | hasCommonCyrillicForm |
P118020
|
FINISHED |
| Object | Валерий |
E1955525
|
NE 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: Валерий | Statement: [Valerii, hasCommonCyrillicForm, Валерий]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonCyrillicForm Context triple: [Valerii, hasCommonCyrillicForm, Валерий]
-
A.
hasCyrillicAlphabetForm
Indicates that an entity has a corresponding representation or form written in the Cyrillic alphabet.
-
B.
hasCommonWritingSystem
Indicates that two entities use the same or mutually intelligible writing system for written communication.
-
C.
hasNameInSlavonic
Indicates that an entity has a specific name or designation expressed in a Slavonic language.
-
D.
CyrillicName
chosen
Indicates that an entity has a name written in the Cyrillic script.
-
E.
hasContextualLetterForms
Indicates that the written form of a letter changes shape depending on its surrounding characters or position within a word.
- F. None of above.
Provenance (4 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01d9ca07b88190b4ad70b6336447b6 |
completed | May 11, 2026, 1:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a71fb7f588190adf020c5d1e9b15a |
completed | June 11, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_6a01d807c3048190b79f0b6b933dd3b7 |
completed | May 11, 2026, 1:22 p.m. |
Created at: April 29, 2026, 9:10 p.m.