Triple
T5881746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Duel |
E130763
|
entity |
| Predicate | mainCharacter |
P1183
|
FINISHED |
| Object | Nadya |
E281523
|
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: Nadya | Statement: [The Duel, mainCharacter, Nadya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nadya Context triple: [The Duel, mainCharacter, Nadya]
-
A.
Natalia
Natalia was a short-lived Boer republic established in the 1830s in what is now KwaZulu-Natal, South Africa.
-
B.
Natalya
chosen
Natalya is a feminine given name of Slavic origin, commonly used in Russian-speaking countries and derived from the Latin name Natalia.
-
C.
Yulia
Yulia is a feminine given name, commonly used in Slavic countries as a form of the name Julia.
-
D.
Katya
Katya is a diminutive and affectionate form of the given name Catherine, commonly used in Slavic and other European cultures.
-
E.
Yelena
Yelena is a feminine given name of Slavic origin, commonly used in Russian-speaking countries and equivalent to Helen or Helena 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03673ecd88190978993056b675259 |
completed | March 22, 2026, 6:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c108039acc8190a5ce23412f1a359c |
completed | March 23, 2026, 9:29 a.m. |
Created at: March 22, 2026, 3:57 p.m.