Triple
T37889021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le goût de la cendre |
E945074
|
entity |
| Predicate | describesThemeOf |
P97400
|
FINISHED |
| Object | Under the Volcano |
—
|
NE NERFINISHED |
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: Under the Volcano | Statement: [Le goût de la cendre, describesThemeOf, Under the Volcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesThemeOf Context triple: [Le goût de la cendre, describesThemeOf, Under the Volcano]
-
A.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
B.
themeExplores
Indicates that a work, action, or discourse centrally examines, investigates, or delves into a particular theme or subject.
-
C.
tacklesTheme
Indicates that one entity addresses, explores, or deals with a particular theme as a central subject.
-
D.
subjectOfDescription
chosen
Indicates that the subject is the main entity being described or characterized in a given context or statement.
-
E.
thematicConcept
Indicates that one entity embodies, expresses, or is centrally concerned with a particular underlying theme or conceptual idea represented by the other 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 3, 2026, 4:19 p.m.