Triple
T35191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easter |
E697
|
entity |
| Predicate | associatedFood |
P1016
|
FINISHED |
| Object | Easter bread |
—
|
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: Easter bread | Statement: [Easter, associatedFood, Easter bread]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedFood Context triple: [Easter, associatedFood, Easter bread]
-
A.
diet
Indicates that an entity regularly consumes a particular type or range of food as its primary source of nutrition.
-
B.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
C.
traditionalCuisine
chosen
Indicates that an entity is associated with the customary or historically rooted style of cooking and food preparation characteristic of a particular culture, region, or community.
-
D.
complements
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
-
E.
fueledBy
Indicates that one entity provides the energy or power source that enables the operation or functioning of 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24989c3308190af59dfae37cfc32f |
completed | Feb. 28, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69a24873e97c8190b9e4279e43b6de14 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.