Triple
T17065947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baker Dill |
E414088
|
entity |
| Predicate | offeredProposal |
P96136
|
FINISHED |
| Object | kill Karen Zariakas’s abusive husband |
—
|
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: kill Karen Zariakas’s abusive husband | Statement: [Baker Dill, offeredProposal, kill Karen Zariakas’s abusive husband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredProposal Context triple: [Baker Dill, offeredProposal, kill Karen Zariakas’s abusive husband]
-
A.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
B.
offeredRewardTo
Indicates that one entity has proposed or promised a reward to another entity, typically as an incentive for a specific action or outcome.
-
C.
offeringOutcome
Indicates the result or consequence that follows from making a particular offering.
-
D.
firstOffered
Indicates that one entity was the earliest or initial provider or proposer of something to another entity or context.
-
E.
hasProposal
chosen
Indicates that an entity possesses, is associated with, or is the subject of a specific proposal.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3db8171348190ab68d2e4f05f7120 |
completed | April 18, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.