Triple
T31213272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blanket Jackson |
E795805
|
entity |
| Predicate | guardianAfterFatherDeath |
P118420
|
FINISHED |
| Object | Katherine Jackson |
—
|
NE NERFINISHED |
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: Katherine Jackson | Statement: [Blanket Jackson, guardianAfterFatherDeath, Katherine Jackson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardianAfterFatherDeath Context triple: [Blanket Jackson, guardianAfterFatherDeath, Katherine Jackson]
-
A.
guardian
Indicates a protective or custodial relationship in which one entity is responsible for the care, safety, or oversight of another.
-
B.
canonicalDeathOfFather
Indicates that the referenced death event is the officially recognized or primary recorded death of the subject’s father.
-
C.
guardedByAfterDeath
Indicates that an entity continues to be guarded or protected by another entity after the former’s death.
-
D.
guardianAppointedFor
chosen
Indicates that one entity has been formally designated as the legal guardian responsible for another entity.
-
E.
afterDeathOf
Indicates that one event, state, or condition occurs subsequent to and as a result of the death of a specified entity.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c28a0e4819099600420cd0da971 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:09 p.m.