Triple
T5386157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nowruz celebrations |
E120203
|
entity |
| Predicate | includesFood |
P56694
|
FINISHED |
| Object | special holiday dishes |
—
|
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: special holiday dishes | Statement: [Nowruz celebrations, includesFood, special holiday dishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFood Context triple: [Nowruz celebrations, includesFood, special holiday dishes]
-
A.
foodItem
Indicates that one entity is a food item that can be eaten or used as food in relation to another entity.
-
B.
foodCustom
Indicates a culturally specific practice, rule, or tradition related to the preparation, serving, or consumption of food.
-
C.
isEatenIn
chosen
Indicates that one entity (typically food) is consumed within the context, location, or occasion specified by another entity.
-
D.
cateringIncludes
Indicates that a catering service or arrangement encompasses or provides the specified item, service, or component as part of its offering.
-
E.
alsoEats
Indicates that an entity consumes something in addition to another item or items it already eats.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd86f6f39c8190aa6af12370e3d12b |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.