Triple
T19927703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Susan Mayer |
E478969
|
entity |
| Predicate | exSpouse |
P23411
|
FINISHED |
| Object | Karl Mayer |
E1403155
|
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: Karl Mayer | Statement: [Susan Mayer, exSpouse, Karl Mayer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Karl Mayer Context triple: [Susan Mayer, exSpouse, Karl Mayer]
-
A.
Karl Mayer
chosen
Karl Mayer is a fictional character from the television series "Desperate Housewives," known as Susan Mayer's ex-husband.
-
B.
Eberhard Klett
Eberhard Klett was an 18th-century German publisher known for issuing Johann Heinrich Lambert’s influential work *Photometria*.
-
C.
Werner Scholl
Werner Scholl was the younger brother of Hans and Sophie Scholl, associated with the White Rose resistance circle in Nazi Germany.
-
D.
Klaus Mayer
Klaus Mayer is a German football executive best known for serving as the chairman of 1. FC Heidenheim.
-
E.
Heinz Bühler
Heinz Bühler is a notable individual who shares the German surname Bühler, recognized as a distinguished bearer of that name.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659cc1a448190aa98d4a66022457e |
completed | April 20, 2026, 4:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07fdc2ce74819084c08e9396bf0dd3 |
completed | May 16, 2026, 5:16 a.m. |
Created at: April 10, 2026, 1:53 p.m.