Triple
T4724677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mai Henry |
E104852
|
entity |
| Predicate | spouseStatusWithJohn W. Henry |
P59049
|
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: [Mai Henry, spouseStatusWithJohn W. Henry, divorced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseStatusWithJohn W. Henry Context triple: [Mai Henry, spouseStatusWithJohn W. Henry, divorced]
-
A.
spouseOfHead
Indicates that one person is the married partner of the individual who holds the position of head (e.g., head of a household, organization, or state).
-
B.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
C.
firstHolderSpouseOf
Indicates that the first holder in the relation is the spouse (married partner) of the other holder.
-
D.
metSpouseAt
Indicates that one person first encountered or became acquainted with their spouse at a particular place, event, or time.
-
E.
spouseNotableFor
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
- F. None of above. chosen
Provenance (4 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_69bd43ed84648190ae0b7ee8e8d00482 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6220071881909670c89d072ffb6d |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd67c895dc8190ba648002ff54424b |
completed | March 20, 2026, 3:29 p.m. |
Created at: March 20, 2026, 1:18 p.m.