Triple
T2872587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sachertorte |
E56797
|
entity |
| Predicate | isEatenOnOccasion |
P14780
|
FINISHED |
| Object | birthdays |
—
|
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: birthdays | Statement: [Sachertorte, isEatenOnOccasion, birthdays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEatenOnOccasion Context triple: [Sachertorte, isEatenOnOccasion, birthdays]
-
A.
eatenOnOccasion
chosen
Indicates that one entity is consumed or eaten by another only at certain times or under specific circumstances, rather than regularly or habitually.
-
B.
servingOccasion
Indicates the occasion, event, or context during which something (typically food or drink) is served.
-
C.
hasAssociatedFeast
Indicates that something (such as a person, event, or entity) is linked to a specific feast or celebratory religious observance.
-
D.
hasStapleFood
Indicates that an entity’s primary or regularly consumed basic food item is another specified entity.
-
E.
servedDuring
Indicates that one entity held a role, position, or performed a function within the time period defined 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abdfe59ef88190b8bdfdd03e8965f3 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.