Triple
T15543095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrovskiy |
E370530
|
entity |
| Predicate | hasTransliterationVariant |
P5923
|
FINISHED |
| Object | Petrovski |
E1163352
|
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: Petrovski | Statement: [Petrovskiy, hasTransliterationVariant, Petrovski]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Petrovski Context triple: [Petrovskiy, hasTransliterationVariant, Petrovski]
-
A.
Petrovich
Petrovich is a Russian patronymic meaning "son of Pyotr (Peter)," commonly used as a middle name in Russian naming conventions.
-
B.
Petrovsky
chosen
Petrovsky is a transliterated Russian surname commonly borne by individuals of Slavic origin and used in various cultural, historical, and geographical contexts.
-
C.
Petrović
Petrović is a common South Slavic surname, notably borne by Croatian basketball legend Dražen Petrović.
-
D.
Petrov
Petrov is an alias or alternate name used by Peter P. Peters.
-
E.
Petar
Petar is a given name commonly used in Slavic countries, equivalent to the English name Peter.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04432c3808190bb5b653bf8de30c6 |
completed | April 16, 2026, 2:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff4c3be1b481909e35094e8088f836 |
completed | May 9, 2026, 3:01 p.m. |
Created at: April 10, 2026, 4:07 a.m.