Triple
T8320104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Here’s Johnny!" scene |
E194807
|
entity |
| Predicate | setDecoration |
P81925
|
FINISHED |
| Object | narrow hotel bathroom |
—
|
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: narrow hotel bathroom | Statement: ["Here’s Johnny!" scene, setDecoration, narrow hotel bathroom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setDecoration Context triple: ["Here’s Johnny!" scene, setDecoration, narrow hotel bathroom]
-
A.
decorationClass
Indicates that one entity serves as a decorative classification or style category applied to another entity.
-
B.
typeOfDecoration
Indicates the specific kind or style of decoration associated with an entity or applied in a given context.
-
C.
valorDecoration
Indicates that an entity has been awarded a decoration or honor specifically in recognition of acts of valor or bravery.
-
D.
relatedDecoration
Indicates that one decoration is associated with, complements, or is contextually linked to another decoration.
-
E.
decorationSystem
Indicates a system or method used to apply, manage, or organize decorative elements in or around an entity.
- 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f6686a0819094abc2bfd2e500a5 |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 5:55 p.m.