Triple
T35200986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeffrey Dahmer |
E1016399
|
entity |
| Predicate | hasSaid |
P88637
|
FINISHED |
| Object | he was driven by compulsions and fantasies |
—
|
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: he was driven by compulsions and fantasies | Statement: [Jeffrey Dahmer, hasSaid, he was driven by compulsions and fantasies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSaid Context triple: [Jeffrey Dahmer, hasSaid, he was driven by compulsions and fantasies]
-
A.
hasSaidToBe
Indicates that one entity is reported or claimed to be another entity, typically based on statements or assertions rather than direct verification.
-
B.
hasSpokenAbout
Indicates that one entity has verbally expressed, discussed, or mentioned another entity or topic.
-
C.
spokenBefore
Indicates that one entity has spoken or produced speech earlier in time than another entity.
-
D.
saidBy
chosen
Indicates that a particular statement, quote, or utterance was spoken or produced by a specific entity.
-
E.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.