Triple
T30390508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles Tuck |
E773067
|
entity |
| Predicate | lostSpouseDueToImmortality |
P95821
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Miles Tuck, lostSpouseDueToImmortality, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostSpouseDueToImmortality Context triple: [Miles Tuck, lostSpouseDueToImmortality, true]
-
A.
spouseDeath
chosen
Indicates that one person's spouse has died, marking the event of the spouse's death in relation to that person.
-
B.
marriedInAfterlifeTo
Indicates that one entity is joined in marriage to another specifically within an afterlife or post-mortem context.
-
C.
spouseFate
Indicates that one person’s fate, status, or outcome is defined specifically in relation to their spouse.
-
D.
spouseDateOfDeath
Indicates the date on which a person's spouse died.
-
E.
marriedToUntilDeathOfSpouse
Indicates a marital relationship that is intended to remain in effect until the death of one of the spouses.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6859bbd7c81909084682a99f2b9be |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:02 p.m.