Triple
T29582124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Torrance about the hotel’s history |
E753615
|
entity |
| Predicate | connectsToLaterEvent |
P54905
|
FINISHED |
| Object | JackAttemptsToMurderFamily |
—
|
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: JackAttemptsToMurderFamily | Statement: [Jack Torrance about the hotel’s history, connectsToLaterEvent, JackAttemptsToMurderFamily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToLaterEvent Context triple: [Jack Torrance about the hotel’s history, connectsToLaterEvent, JackAttemptsToMurderFamily]
-
A.
coversEventsAfter
Indicates that one event or time interval extends to include all events occurring after a specified reference event or time.
-
B.
laterRelatedEvent
chosen
Indicates that one event is temporally related to another by occurring at a later time.
-
C.
connectedToEvent
Indicates that an entity has a direct association or linkage with a specific event.
-
D.
eventualSuccessor
Indicates that one entity will become the successor of another at some later point in time, rather than immediately.
-
E.
isLinkedToEvent
Indicates that an entity has an association or connection with a specific event.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: April 28, 2026, 6:07 p.m.