Triple
T1776300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speed Stick |
E38986
|
entity |
| Predicate | hasScent |
P23045
|
FINISHED |
| Object | fresh scent |
—
|
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: fresh scent | Statement: [Speed Stick, hasScent, fresh scent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScent Context triple: [Speed Stick, hasScent, fresh scent]
-
A.
hasFragrance
chosen
Indicates that one entity possesses or emits a particular scent or aroma associated with another entity.
-
B.
olfactoryFamily
Indicates a relationship where one entity belongs to, or is categorized within, a particular olfactory family or scent classification defined by the other entity.
-
C.
hasSpray
Indicates that one entity possesses, contains, or is equipped with a spray or spraying capability in relation to another entity or context.
-
D.
odor
Indicates that one entity emits, possesses, or is characterized by a particular smell detectable by another entity.
-
E.
hasLuster
Indicates that one entity possesses a shiny, glossy, or reflective surface quality.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.