Triple
T13566571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borys Paton |
E324051
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Borys |
E74996
|
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: Borys | Statement: [Borys Paton, givenName, Borys]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Borys Context triple: [Borys Paton, givenName, Borys]
-
A.
Vitaly
Vitaly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
B.
Grigory
Grigory is a masculine given name of Russian origin, historically borne by notable figures such as statesman and nobleman Grigory Orlov.
-
C.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
D.
Ryhor Baradulin
Ryhor Baradulin was a prominent Belarusian poet, translator, and public figure, widely regarded as one of the leading voices of 20th-century Belarusian literature.
-
E.
Boris
chosen
Boris is the given name of Boris Johnson, the former Prime Minister of the United Kingdom and prominent British Conservative politician.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00cecd48190a9a2caff3d424817 |
completed | April 12, 2026, 2:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76bb3d77c8190a7af2ee7e9b6748a |
completed | May 3, 2026, 3:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.