Triple
T2673061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fanny Koch |
E56392
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Rudolf Einstein |
E53414
|
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: Rudolf Einstein | Statement: [Fanny Koch, spouse, Rudolf Einstein]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rudolf Einstein Context triple: [Fanny Koch, spouse, Rudolf Einstein]
-
A.
Rudolf Einstein
chosen
Rudolf Einstein was the father of Elsa Einstein, who was both the second wife and cousin of physicist Albert Einstein.
-
B.
Eduard Einstein
Eduard Einstein was the younger son of physicist Albert Einstein, known for his early promise in psychiatry and his later struggles with severe mental illness.
-
C.
Klaus Martin Einstein
Klaus Martin Einstein was one of the sons of physicist Hans Albert Einstein and a grandson of Albert Einstein.
-
D.
Hermann Einstein
Hermann Einstein was a German engineer and businessman best known as the father of physicist Albert Einstein.
-
E.
Bernhard Caesar Einstein
Bernhard Caesar Einstein was a Swiss-American engineer and the only grandchild of Albert Einstein to become a physicist.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9b08b1c8190824342fc63e555d2 |
completed | March 7, 2026, 7:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afce812640819085c46f7452b5913b |
completed | March 10, 2026, 7:55 a.m. |
Created at: March 6, 2026, 9:54 p.m.