Triple
T5747098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amorphophallus titanum |
E126761
|
entity |
| Predicate | odorResembles |
P6479
|
FINISHED |
| Object | rotting flesh |
—
|
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: rotting flesh | Statement: [Amorphophallus titanum, odorResembles, rotting flesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: odorResembles Context triple: [Amorphophallus titanum, odorResembles, rotting flesh]
-
A.
odor
chosen
Indicates that one entity emits, possesses, or is characterized by a particular smell detectable by another entity.
-
B.
odorResponse
Indicates a relationship where an entity exhibits a measurable reaction or change in behavior, physiology, or activity in response to an odor stimulus.
-
C.
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.
-
D.
senseOfSmell
Indicates that one entity has the ability to detect or perceive odors or scents through the sense of smell.
-
E.
drunkBy
Indicates that a substance or beverage is consumed by a particular 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.