Triple
T20997092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellen Lundström |
E517176
|
entity |
| Predicate | maritalStatusWithIngmarBergman |
P5173
|
FINISHED |
| Object | divorced |
—
|
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: divorced | Statement: [Ellen Lundström, maritalStatusWithIngmarBergman, divorced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalStatusWithIngmarBergman Context triple: [Ellen Lundström, maritalStatusWithIngmarBergman, divorced]
-
A.
marital status
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
B.
spouseStatus
chosen
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not married to each other.
-
C.
maritalPeriodWith
Indicates the time span during which two entities were married to each other.
-
D.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
E.
marriedIn
Indicates that two entities entered into a marital relationship at a specific place or within a particular jurisdiction.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc21838081909872eed21bc12a08 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:51 p.m.