Triple
T25335204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johanna Maria Magdalena Ritschel |
E635256
|
entity |
| Predicate | spouseAtMarriage |
P44979
|
FINISHED |
| Object | Günther Quandt |
—
|
NE NERFINISHED |
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: Günther Quandt | Statement: [Johanna Maria Magdalena Ritschel, spouseAtMarriage, Günther Quandt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseAtMarriage Context triple: [Johanna Maria Magdalena Ritschel, spouseAtMarriage, Günther Quandt]
-
A.
spouseNameAtMarriage
chosen
Indicates the full name a person’s spouse had at the time of their marriage.
-
B.
spouseStatusAtMarriage
Indicates the marital status each partner held at the time their marriage to one another was formed.
-
C.
metSpouseAt
Indicates that one person first encountered or became acquainted with their spouse at a particular place, event, or time.
-
D.
spouseAtEvent
Indicates that two individuals are spouses who are present together at a specific event.
-
E.
spouse name
Indicates that one entity is the legally recognized husband or wife of the other, specifying the partner’s name in a marital relationship.
- F. None of above.
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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 21, 2026, 1:32 p.m.