Triple
T11913624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilona Duczynska |
E283455
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Ilona |
E938360
|
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: Ilona | Statement: [Ilona Duczynska, givenName, Ilona]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ilona Context triple: [Ilona Duczynska, givenName, Ilona]
-
A.
Ilona
chosen
Ilona is a key supporting protagonist and skilled Atlas operative in the video game Call of Duty: Advanced Warfare.
-
B.
Emilija
Emilija is a feminine given name commonly used in various Slavic and Baltic countries, equivalent to Emilia or Emily in English.
-
C.
Rositsa
Rositsa is a river in northern Bulgaria that serves as a significant tributary of the Yantra River.
-
D.
Iola Tornagi
Iola Tornagi was the wife of renowned Russian opera bass Feodor Chaliapin and a figure associated with his personal and artistic life.
-
E.
Bronislava
Bronislava is a feminine given name of Slavic origin, notably borne by the influential ballet dancer and choreographer Bronislava Nijinska.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e52a2bc08190b80cc6ccf5779d7c |
completed | April 10, 2026, 11:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f4186938548190b5ae10e111aece9a |
completed | May 1, 2026, 3:05 a.m. |
Created at: April 8, 2026, 9:44 p.m.