Triple
T12552646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | involuntary memory |
E300133
|
entity |
| Predicate | isTriggeredBy |
P55105
|
FINISHED |
| Object | smells |
—
|
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: smells | Statement: [involuntary memory, isTriggeredBy, smells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTriggeredBy Context triple: [involuntary memory, isTriggeredBy, smells]
-
A.
hasTriggerType
Indicates that an event, condition, or mechanism is associated with a specific type or category of trigger that initiates it.
-
B.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
C.
usesTriggerSystem
Indicates that one entity operates or functions by means of a trigger-based mechanism or system provided or associated with another entity.
-
D.
triggeredFires
Indicates that one entity caused or initiated the occurrence of one or more fires in another entity or location.
-
E.
triggeredFrom
chosen
Indicates that one event, action, or process was initiated or caused as a result of another specific event, action, or process.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:58 p.m.