Triple
T17779886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wax Room |
E443866
|
entity |
| Predicate | sensoryModalitiesEngaged |
P123106
|
FINISHED |
| Object | smell |
—
|
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: smell | Statement: [Wax Room, sensoryModalitiesEngaged, smell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensoryModalitiesEngaged Context triple: [Wax Room, sensoryModalitiesEngaged, smell]
-
A.
sensoryModality
chosen
Indicates the type of sensory channel (e.g., visual, auditory, tactile) through which an experience, perception, or information is received or processed.
-
B.
sensoryCommunication
Indicates a relationship where one entity conveys or exchanges information with another through sensory signals or perception-based means.
-
C.
senses
Indicates that an entity perceives or detects another entity or stimulus through one of its senses.
-
D.
sensorySystem
Indicates that one entity functions as the sensory system (or part of it) of another, enabling the detection and processing of internal or external stimuli.
-
E.
providesSensoryEffects
Indicates that one entity causes or contributes to sensory experiences or perceptions in another entity.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48720734c819085ebe37065b8c8f3 |
completed | April 19, 2026, 7:41 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.