Triple
T35162700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Addie Langdon |
E1015310
|
entity |
| Predicate | isPreventedFrom |
P12127
|
FINISHED |
| Object | dying on Murder House property |
—
|
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: dying on Murder House property | Statement: [Addie Langdon, isPreventedFrom, dying on Murder House property]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPreventedFrom Context triple: [Addie Langdon, isPreventedFrom, dying on Murder House property]
-
A.
isPreventableBy
Indicates that the occurrence or effect of one entity can be avoided or stopped through the action, intervention, or influence of another entity.
-
B.
prevented
chosen
Indicates that one entity stopped, hindered, or made it impossible for another entity or event to occur or proceed.
-
C.
isProhibitedFor
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
D.
doesNotPrevent
Indicates that one entity or condition fails to stop, block, or inhibit another event, action, or state from occurring.
-
E.
isDeniedBy
Indicates that a request, claim, or action directed at an entity is explicitly refused or rejected by 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_69f76ddbfde081908bffc91572368289 |
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.