Triple
T25402443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ковальский |
E636460
|
entity |
| Predicate | транслитерация на латиницу |
P44932
|
FINISHED |
| Object | Kovalski |
—
|
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: Kovalski | Statement: [Ковальский, транслитерация на латиницу, Kovalski]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: транслитерация на латиницу Context triple: [Ковальский, транслитерация на латиницу, Kovalski]
-
A.
standardTransliteration
chosen
Indicates that one representation of text is a transliteration of another according to a recognized standard or convention.
-
B.
alternativeTransliteration
Indicates that one written form represents an alternative way of transliterating the same original text or name into another script or orthography.
-
C.
commonTransliterationSystem
Indicates that two or more written forms are derived using the same standardized system for converting text from one script to another.
-
D.
transliterationTarget
Indicates that one entity is the target script or form into which another entity is transliterated.
-
E.
formerTransliteration
Indicates that one transliteration was previously used for an entity but has since been replaced by a different transliteration.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f584fbde0c8190ac451fe33848aadb |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:52 p.m.