Triple
T10311620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dimitri Portwood Kutcher |
E241903
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Dimitri |
E243753
|
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: Dimitri | Statement: [Dimitri Portwood Kutcher, givenName, Dimitri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dimitri Context triple: [Dimitri Portwood Kutcher, givenName, Dimitri]
-
A.
Dimitri
chosen
Dimitri is a masculine given name of Greek origin, commonly used in various cultures and languages.
-
B.
Grigory
Grigory is a masculine given name of Russian origin, historically borne by notable figures such as statesman and nobleman Grigory Orlov.
-
C.
Anatoly
Anatoly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
D.
Nikolay
Nikolay is a masculine given name of Slavic origin, commonly used in Russian-speaking countries and equivalent to Nicholas in English.
-
E.
Nikolai
Nikolai is a recurring Russian ally and pilot in the Call of Duty: Modern Warfare series, known for assisting the main protagonists with transport and intelligence.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d32ac6c08190b23eb042b3ec284a |
completed | April 7, 2026, 9:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de54d83e44819097abf6714bd48680 |
completed | April 14, 2026, 2:53 p.m. |
Created at: April 6, 2026, 11:48 a.m.