Triple
T28070575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sense of Taste |
E709384
|
entity |
| Predicate | allegorizes |
P129
|
FINISHED |
| Object | bodily sense of taste |
—
|
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: bodily sense of taste | Statement: [The Sense of Taste, allegorizes, bodily sense of taste]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegorizes Context triple: [The Sense of Taste, allegorizes, bodily sense of taste]
-
A.
allegoricalInterpretation
Indicates that one entity is interpreted as symbolically representing deeper, often moral or spiritual, meanings within another entity (such as a text, image, or event).
-
B.
politicalAllegoryFor
Indicates that one entity symbolically represents or critiques another entity, event, or system within a political context.
-
C.
allegoricalDomain
Indicates that one entity serves as the abstract or symbolic domain that another entity allegorically represents or refers to.
-
D.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
E.
hasAllegoricalDepictionsBy
Indicates that one entity is represented through allegorical depictions created by another 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 8:45 p.m.