Triple
T25641202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marlboro Ice |
E642839
|
entity |
| Predicate | hasSensoryProfile |
P93007
|
FINISHED |
| Object | strong cooling effect |
—
|
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: strong cooling effect | Statement: [Marlboro Ice, hasSensoryProfile, strong cooling effect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSensoryProfile Context triple: [Marlboro Ice, hasSensoryProfile, strong cooling effect]
-
A.
hasSensibility
Indicates that an entity possesses awareness, responsiveness, or sensitivity to stimuli or experiences.
-
B.
hasAbilityProfile
Indicates that an entity is associated with a specific set or profile of abilities, skills, or capabilities.
-
C.
hasSensation
chosen
Indicates that an entity experiences or is subject to a particular sensory or perceptual feeling.
-
D.
sensoryModality
Indicates the type of sensory channel (e.g., visual, auditory, tactile) through which an experience, perception, or information is received or processed.
-
E.
hasSensor
Indicates that one entity is equipped with, contains, or uses a particular sensor.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 21, 2026, 5:43 p.m.