Triple
T33230811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | piperade |
E850686
|
entity |
| Predicate | traditionalSeasoning |
P102161
|
FINISHED |
| Object | salt |
—
|
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: salt | Statement: [piperade, traditionalSeasoning, salt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalSeasoning Context triple: [piperade, traditionalSeasoning, salt]
-
A.
seasoningType
Indicates the specific kind or category of seasoning associated with an item or preparation.
-
B.
seasoningStyle
Indicates the characteristic way in which an item is flavored or seasoned, such as the method, intensity, or cultural style of its seasoning.
-
C.
typicalSpices
chosen
Indicates that certain spices are commonly or characteristically used in association with a particular dish, cuisine, or ingredient.
-
D.
traditionalAccompaniment
Indicates that one entity is customarily or culturally served, used, or presented together with another as its traditional accompaniment.
-
E.
traditionalCuisine
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.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 1, 2026, 1:30 a.m.