Triple
T18768913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicken Marengo |
E458961
|
entity |
| Predicate | historicalDish |
P133465
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Chicken Marengo, historicalDish, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalDish Context triple: [Chicken Marengo, historicalDish, true]
-
A.
traditionalDish
Indicates that the object is a dish customarily prepared, eaten, or recognized within the subject’s cultural or regional tradition.
-
B.
traditionalFoodBase
Indicates that one entity serves as the primary ingredient, staple, or foundational component of a traditional food associated with another entity.
-
C.
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.
-
D.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
E.
knownForDish
Indicates that an entity is recognized or notable for preparing, serving, or being associated with a particular dish.
- F. None of above. chosen
Provenance (4 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d867264819098ae35c9feab3bb4 |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:52 a.m.