Triple
T29582119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Torrance about the hotel’s history |
E753615
|
entity |
| Predicate | warningDeliveredBy |
P86402
|
FINISHED |
| Object | hotelManagement |
—
|
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: hotelManagement | Statement: [Jack Torrance about the hotel’s history, warningDeliveredBy, hotelManagement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warningDeliveredBy Context triple: [Jack Torrance about the hotel’s history, warningDeliveredBy, hotelManagement]
-
A.
warningGivenBy
chosen
Indicates that one entity issues or delivers a warning to another entity.
-
B.
warningRecipient
Indicates that one entity is the recipient or target audience of a warning issued by another entity.
-
C.
warningType
Indicates the specific category or classification of a warning associated with an entity or event.
-
D.
warningIssued
Indicates that a formal warning or alert has been communicated from one entity to another regarding a potential or existing risk, problem, or violation.
-
E.
warningOutcome
Indicates that a warning event leads to, results in, or is associated with a particular outcome or consequence.
- 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_69f66d7b547c8190ba4bfef5c7567a77 |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:07 p.m.