Triple
T32004267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemures |
E817217
|
entity |
| Predicate | consequenceIfNotAppeased |
P180659
|
FINISHED |
| Object | haunt the living |
—
|
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: haunt the living | Statement: [Lemures, consequenceIfNotAppeased, haunt the living]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceIfNotAppeased Context triple: [Lemures, consequenceIfNotAppeased, haunt the living]
-
A.
unexpectedConsequenceOf
Indicates that one event, action, or condition occurs as an unforeseen or unintended result of another.
-
B.
avoidedConsequence
Indicates that an action or event prevented a particular consequence from occurring.
-
C.
consequenceOfKilling
Indicates that one event or state occurs as a direct result of an act of killing.
-
D.
announcedConsequence
Indicates that one entity has publicly stated or declared a specific outcome or consequence that will result from an action, event, or condition.
-
E.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
- F. None of above. chosen
Provenance (4 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: May 1, 2026, 12:14 a.m.