Triple
T2946774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbara Müller |
E79520
|
entity |
| Predicate | maritalStatusBeforeKepler |
P20884
|
FINISHED |
| Object | widow |
—
|
LITERAL 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: widow | Statement: [Barbara Müller, maritalStatusBeforeKepler, widow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalStatusBeforeKepler Context triple: [Barbara Müller, maritalStatusBeforeKepler, widow]
-
A.
marriedBefore
Indicates that one entity entered into a marriage at an earlier time than the other entity.
-
B.
marital status
chosen
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
C.
spouseStatus
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not married to each other.
-
D.
marriedAfter
Indicates that one marriage occurred later in time than another specified marriage.
-
E.
metSpouseAt
Indicates that one person first encountered or became acquainted with their spouse at a particular place, event, or time.
- 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98b3f86c819094526c2af611bfb5 |
completed | March 8, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.