Triple
T25069187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Werther Fever |
E627861
|
entity |
| Predicate | allegedlyCaused |
P10554
|
FINISHED |
| Object | imitative suicides among young readers |
—
|
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: imitative suicides among young readers | Statement: [Werther Fever, allegedlyCaused, imitative suicides among young readers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedlyCaused Context triple: [Werther Fever, allegedlyCaused, imitative suicides among young readers]
-
A.
eligibleCause
Indicates that one entity qualifies as a valid or acceptable cause or reason for another entity or outcome.
-
B.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
debatedAsCauseOf
chosen
Indicates that one entity is discussed or argued over as a possible cause or origin of another entity.
-
D.
possibleCauseOf
Indicates that one entity is a potential, but not certain, cause or contributing factor to another entity or outcome.
-
E.
allegedAction
Indicates that an action is claimed or asserted to have occurred, typically without being proven or confirmed.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6:10 a.m.