Triple
T10201008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Promises |
E238879
|
entity |
| Predicate | character |
P662
|
FINISHED |
| Object | Kirill |
E662060
|
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: Kirill | Statement: [Eastern Promises, character, Kirill]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kirill Context triple: [Eastern Promises, character, Kirill]
-
A.
Kirill
Kirill is a highly skilled Russian assassin and primary antagonist who relentlessly hunts Jason Bourne in the action thriller film "The Bourne Supremacy."
-
B.
Kirill
chosen
Kirill is a masculine given name of Slavic origin, commonly used in Russian-speaking and other Eastern European countries.
-
C.
Timofei
Timofei is a masculine given name of Slavic origin, commonly used in Russian-speaking countries and related to the name Timo.
-
D.
Vova
Vova is a common Russian diminutive form of the male given name Vladimir.
-
E.
Nikolay
Nikolay is a masculine given name of Slavic origin, commonly used in Russian-speaking countries and equivalent to Nicholas in English.
- 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_69ca84e1ea088190b38162e43d4cfa8f |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdee40cb7481908a1bf4d5636eb8ef |
completed | April 2, 2026, 4:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d317f40f0c8190a3d966c934cc20f7 |
completed | April 6, 2026, 2:18 a.m. |
Created at: March 30, 2026, 9:14 p.m.