Triple
T38674094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Balfour |
E943680
|
entity |
| Predicate | notableVictimRelative |
P206611
|
FINISHED |
| Object | Jennifer Hudson |
E4614
|
NE 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: Jennifer Hudson | Statement: [William Balfour, notableVictimRelative, Jennifer Hudson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVictimRelative Context triple: [William Balfour, notableVictimRelative, Jennifer Hudson]
-
A.
notableRelative
Indicates that an entity has a relative who is notable or well-known, specifying that familial relationship.
-
B.
victimRelation
Indicates that one entity is the victim or target of harm, wrongdoing, or an adverse action caused by another entity.
-
C.
familyNotableMember
Indicates that a particular individual is a distinguished or noteworthy member of a given family.
-
D.
familyNotableRole
Indicates that a member of the family holds or held a particularly significant, distinguished, or influential role.
-
E.
spouseRelative
Indicates that one person is related to another through the marriage of at least one of them (e.g., in-laws or relatives by marriage).
- F. None of above. chosen
Provenance (5 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4205c030e08190ac9f9e966117589e |
completed | June 29, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:33 p.m.