Triple
T3182361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brenda Quagmire |
E66618
|
entity |
| Predicate | hasStoryline |
P24126
|
FINISHED |
| Object | domestic abuse by boyfriend |
—
|
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: domestic abuse by boyfriend | Statement: [Brenda Quagmire, hasStoryline, domestic abuse by boyfriend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStoryline Context triple: [Brenda Quagmire, hasStoryline, domestic abuse by boyfriend]
-
A.
storyline
chosen
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
B.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
C.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
D.
hasAllyInStory
Indicates that one entity is portrayed as an ally or supportive partner of another entity within the context of a specific story or narrative.
-
E.
storyBy
Indicates that one entity is the creator or author of the story associated with another 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6bd07888190b680eace8290d821 |
completed | March 8, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.