Triple
T24780521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold Room |
E619982
|
entity |
| Predicate | notableSceneWithCharacter |
P128577
|
FINISHED |
| Object | Jack Torrance |
—
|
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: Jack Torrance | Statement: [Gold Room, notableSceneWithCharacter, Jack Torrance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSceneWithCharacter Context triple: [Gold Room, notableSceneWithCharacter, Jack Torrance]
-
A.
notableScene
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
-
B.
notableSceneAssociation
chosen
Indicates an association between an entity and a notable or memorable scene in which it prominently appears or plays a significant role.
-
C.
notableLabelScene
Indicates that a particular scene is notably associated with, or prominently labeled by, a specific tag, title, or descriptor.
-
D.
notableAppearance
Indicates that an entity is prominently featured or makes a significant appearance in another work, event, or context.
-
E.
notableAppearanceIn
Indicates that an entity is prominently featured or plays a significant role in a particular work, event, or context.
- 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_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 18, 2026, 4:44 a.m.