Triple
T32908486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rovno |
E841806
|
entity |
| Predicate | standardizedNameInRussian |
P20560
|
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: [Rovno, standardizedNameInRussian, Ровно]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizedNameInRussian Context triple: [Rovno, standardizedNameInRussian, Ровно]
-
A.
currentNameInRussian
Indicates the current official name of an entity as expressed in the Russian language.
-
B.
nameInRussian
chosen
Indicates that an entity is known or referred to by a specific name when expressed in the Russian language.
-
C.
CyrillicName
Indicates that an entity has a name written in the Cyrillic script.
-
D.
hasNameInRusyn
Indicates that an entity has a specific name or label expressed in the Rusyn language.
-
E.
nameInLanguageRomanization
Indicates that an entity’s name is represented in the romanized (Latin-script) form of a particular language.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:19 a.m.