Triple
T20592438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katherine MacGregor |
E505962
|
entity |
| Predicate | marriageStatusWithBertRemsen |
P107707
|
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: [Katherine MacGregor, marriageStatusWithBertRemsen, divorced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageStatusWithBertRemsen Context triple: [Katherine MacGregor, marriageStatusWithBertRemsen, divorced]
-
A.
hasMaritalStatusAtEnd
chosen
Indicates that an entity possesses a specific marital status at the end of a given period, event, or reference time.
-
B.
marriageStatusChange
Indicates a change in an entity’s marital status from one state to another at a particular point in time.
-
C.
parentsMarriageStatus
Indicates the marital status relationship between an individual’s parents (e.g., married, divorced, separated, never married).
-
D.
spouseStatusAtMarriage
Indicates the marital status each partner held at the time their marriage to one another was formed.
-
E.
resultedInMarriageTo
Indicates that one event, action, or circumstance led to or caused a marriage to occur between the related entities.
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a97d63cc8190853e052d5930470d |
completed | April 20, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.