Triple
T33346104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allium |
E853798
|
entity |
| Predicate | characteristicOdor |
P152625
|
FINISHED |
| Object | pungent sulfurous 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: pungent sulfurous smell | Statement: [Allium, characteristicOdor, pungent sulfurous smell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characteristicOdor Context triple: [Allium, characteristicOdor, pungent sulfurous smell]
-
A.
characteristicAroma
chosen
Indicates that one entity has a distinctive smell or scent that characterizes or is typically associated with another entity.
-
B.
senseOfSmell
Indicates that one entity has the ability to detect or perceive odors or scents through the sense of smell.
-
C.
hasSulfurOdor
Indicates that an entity emits or possesses an odor characteristic of sulfur or sulfur-containing compounds.
-
D.
odor
Indicates that one entity emits, possesses, or is characterized by a particular smell detectable by another entity.
-
E.
commonScents
Indicates that two or more entities share the same or very similar smells or fragrances.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 1, 2026, 1:34 a.m.