Triple
T30390526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles Tuck |
E773067
|
entity |
| Predicate | spouseReactionToImmortality |
P191797
|
FINISHED |
| Object | left him |
—
|
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: left him | Statement: [Miles Tuck, spouseReactionToImmortality, left him]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseReactionToImmortality Context triple: [Miles Tuck, spouseReactionToImmortality, left him]
-
A.
spouseFate
Indicates that one person’s fate, status, or outcome is defined specifically in relation to their spouse.
-
B.
marriedInAfterlifeTo
Indicates that one entity is joined in marriage to another specifically within an afterlife or post-mortem context.
-
C.
spouseTransformedInto
Indicates that one spouse in a marital relationship has been changed or converted into a different form, state, or entity.
-
D.
subsequentReactionToHusbandsDeath
Indicates a reaction or response that occurs after and as a result of the husband's death.
-
E.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: April 29, 2026, 8:02 p.m.