Triple
T28304252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smirnov |
E713795
|
entity |
| Predicate | orthographicFormInRussian |
P33995
|
FINISHED |
| Object | Смирнов |
—
|
NE NERFINISHED |
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: [Smirnov, orthographicFormInRussian, Смирнов]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orthographicFormInRussian Context triple: [Smirnov, orthographicFormInRussian, Смирнов]
-
A.
hasOrthographicReform
Indicates that an entity has undergone or is associated with a change or standardization in its writing system or spelling conventions.
-
B.
orthographicVariant
chosen
Indicates that two written forms are different spellings or orthographic representations of the same linguistic item.
-
C.
roleInOrthography
Indicates the specific function or contribution an element has within a given writing system or orthographic structure.
-
D.
orthographicIndependence
Indicates that one writing system or orthographic form functions independently of, and is not derived from or constrained by, another.
-
E.
accentedFormOf
Indicates that one linguistic form is an accented or diacritically marked variant of another, more basic form.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 11:36 p.m.