Triple
T6324019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konstantin |
E141815
|
entity |
| Predicate | hasAlternativeTransliteration |
P5923
|
FINISHED |
| Object | Konstantyn |
E141815
|
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: Konstantyn | Statement: [Konstantin, hasAlternativeTransliteration, Konstantyn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Konstantyn Context triple: [Konstantin, hasAlternativeTransliteration, Konstantyn]
-
A.
Konstantin
chosen
Konstantin is a masculine given name of Latin origin, widely used in Slavic and other European cultures, meaning “steadfast” or “constant.”
-
B.
Vladislav
Vladislav is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
C.
Prince of Halych
The Prince of Halych was the medieval ruler of the principality of Halych in what is now western Ukraine, a key political and cultural center in the Kingdom of Galicia–Volhynia.
-
D.
Bronisław
Bronisław is a masculine Slavic given name, particularly common in Poland, borne by several notable historical and cultural figures.
-
E.
Włodzimierz
Włodzimierz is the Polish form of the Slavic given name Vladimir, commonly used in Poland.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064e538ac81908c5d7556513c2bc3 |
completed | March 22, 2026, 9:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c62d3a68f881908de1d9e70e00cb02 |
completed | March 27, 2026, 7:09 a.m. |
Created at: March 22, 2026, 4:29 p.m.