Triple
T1035752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konstantin Chernenko |
E22357
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Konstantin |
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: Konstantin | Statement: [Konstantin Chernenko, givenName, Konstantin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Konstantin Context triple: [Konstantin Chernenko, givenName, Konstantin]
-
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.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
C.
Vladimir
Vladimir is a common Russian male given name of Slavic origin, historically associated with rulers and notably borne by Russian president Vladimir Putin.
-
D.
Gavril
Gavril is a masculine given name, commonly used in Slavic and Eastern European cultures, that derives from the Hebrew name Gabriel.
-
E.
Leonid
Leonid is a masculine given name of Slavic origin, notably borne by Soviet leader Leonid Brezhnev.
- 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b816272c8190a12e470c4d4ebcf9 |
completed | March 1, 2026, 10:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adf3a5cac081908d655e42a58a81c5 |
completed | March 8, 2026, 10:09 p.m. |
Created at: March 1, 2026, 7:41 p.m.