Triple
T35200983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeffrey Dahmer |
E1016399
|
entity |
| Predicate | dischargeReason |
P41278
|
FINISHED |
| Object | alcohol abuse |
—
|
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: alcohol abuse | Statement: [Jeffrey Dahmer, dischargeReason, alcohol abuse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dischargeReason Context triple: [Jeffrey Dahmer, dischargeReason, alcohol abuse]
-
A.
dischargeType
Indicates the manner or category of how something is released, emitted, or discharged from a source.
-
B.
dischargeStatus
Indicates the current state or outcome of an entity’s release or discharge from a prior condition, process, or obligation.
-
C.
reasonForDismissal
chosen
Indicates the cause or justification for which an entity (such as a person, case, or item) was dismissed, terminated, or removed.
-
D.
reasonForStay
Indicates the underlying cause, purpose, or circumstance that explains why an entity remains or is staying in a particular place or situation.
-
E.
hasDischarge
Indicates that one entity releases, emits, or expels a substance, energy, or flow from itself.
- 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_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.