Triple
T24780567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | red bathroom in the Overlook Hotel |
E619983
|
entity |
| Predicate | notableDialogueWith |
P61643
|
FINISHED |
| Object | Delbert Grady |
—
|
NE NERFINISHED |
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: Delbert Grady | Statement: [red bathroom in the Overlook Hotel, notableDialogueWith, Delbert Grady]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDialogueWith Context triple: [red bathroom in the Overlook Hotel, notableDialogueWith, Delbert Grady]
-
A.
notableInterviewee
Indicates that a person has been interviewed by another person or organization in a way considered significant or noteworthy.
-
B.
notableFriend
Indicates that one entity is a friend of another in a way that is especially prominent, well-known, or significant.
-
C.
notableEncounterWith
chosen
Indicates that an entity has had a significant or noteworthy meeting, interaction, or confrontation with another entity.
-
D.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
notablePersonDiscussed
Indicates that the subject entity includes or features a discussion about the referenced notable person.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 18, 2026, 4:44 a.m.