Triple
T13686065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergius |
E328128
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Sergiyos |
E325060
|
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: Sergiyos | Statement: [Sergius, hasVariant, Sergiyos]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sergiyos Context triple: [Sergius, hasVariant, Sergiyos]
-
A.
Sergy
Sergy is a small commune in the Ain department of eastern France, located near the Swiss border in the Pays de Gex region.
-
B.
Sergiy
chosen
Sergiy is a given name, commonly used as a Ukrainian or Eastern European variant of the name Sergei.
-
C.
Grigor
Grigor is a given name, commonly used in various Eastern European and Caucasian cultures, that corresponds to the English name Gregory.
-
D.
Tymofiy
Tymofiy is a masculine given name of Ukrainian origin, notably borne by economist and former Ukrainian minister Tymofiy Mylovanov.
-
E.
Grigory
Grigory is a masculine given name of Russian origin, historically borne by notable figures such as statesman and nobleman Grigory Orlov.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66f8acc8190b2a82b722930b995 |
completed | April 12, 2026, 4:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c0db310c81909c22507f9a3e7dee |
completed | May 3, 2026, 9:40 p.m. |
Created at: April 9, 2026, 9:53 p.m.