Triple
T15039650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Secret History |
E378565
|
entity |
| Predicate | hasMotiveForMurder |
P34163
|
FINISHED |
| Object | fear of exposure and social ruin |
—
|
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: fear of exposure and social ruin | Statement: [The Secret History, hasMotiveForMurder, fear of exposure and social ruin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMotiveForMurder Context triple: [The Secret History, hasMotiveForMurder, fear of exposure and social ruin]
-
A.
reasonForMurder
chosen
Indicates the motive or underlying cause that led someone to commit a murder.
-
B.
hasMotiveOfCriminals
Indicates that the specified motive is attributed to or associated with the criminals in question.
-
C.
allegedToHaveKilled
Indicates that one entity is claimed or accused, but not proven, to have killed another entity.
-
D.
estimatedMurdersCommitted
Indicates an approximate count of murders that are believed or inferred to have been committed by an entity.
-
E.
hasSerialKiller
Indicates that one entity is a serial killer associated with, responsible for, or targeting 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded82e79a481908ddb9609af8c4407 |
completed | April 15, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 3 a.m.