Triple
T35807078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Brothers of Destruction |
E1035128
|
entity |
| Predicate | storylineFamilyMember |
P184664
|
FINISHED |
| Object | Paul Bearer |
—
|
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: Paul Bearer | Statement: [The Brothers of Destruction, storylineFamilyMember, Paul Bearer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storylineFamilyMember Context triple: [The Brothers of Destruction, storylineFamilyMember, Paul Bearer]
-
A.
familyPlanningStoryline
Indicates a narrative or sequence of events centered on decisions, actions, and experiences related to family planning.
-
B.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
C.
familyDescription
Indicates a descriptive statement that characterizes or summarizes the nature, structure, or dynamics of a family relationship.
-
D.
hasProtagonistFamilyMember
Indicates that a work’s protagonist has a specified individual as a member of their family.
-
E.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:06 p.m.