Triple
T9747094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fyodor |
E236337
|
entity |
| Predicate | relatedName |
P3889
|
FINISHED |
| Object | Teodor |
E270314
|
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: Teodor | Statement: [Fyodor, relatedName, Teodor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Teodor Context triple: [Fyodor, relatedName, Teodor]
-
A.
Teodor
chosen
Teodor is a given name, commonly used in various European languages, that corresponds to the English name Theodore.
-
B.
Theodor
Theodor "Ted" Nelson is an American pioneer of information technology best known for coining the term "hypertext" and envisioning global hyperlinked document systems.
-
C.
Theodor
Theodor is the given name of Emil Theodor Kocher, a Swiss surgeon and Nobel laureate renowned for his pioneering work in thyroid surgery.
-
D.
Eduard
Eduard was the younger son of physicist Albert Einstein, known for his promising studies in psychiatry and his lifelong struggle with schizophrenia.
-
E.
Eduard
Eduard is a central character in Paulo Coelho’s novel "Veronika Decides to Die," portrayed as a sensitive, introspective young man whose relationship with the protagonist profoundly influences her view of life and death.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f677830819096d388b9c798ecd5 |
completed | April 1, 2026, 10:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1bcd2e08c8190808b58fdabe0c9d3 |
completed | April 5, 2026, 1:37 a.m. |
Created at: March 30, 2026, 8:23 p.m.