Triple
T18768903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicken Marengo |
E458961
|
entity |
| Predicate | traditionalGarnish |
P56695
|
FINISHED |
| Object | fried eggs |
—
|
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: fried eggs | Statement: [Chicken Marengo, traditionalGarnish, fried eggs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalGarnish Context triple: [Chicken Marengo, traditionalGarnish, fried eggs]
-
A.
isTypicallyGarnishedWith
chosen
Indicates that one item is commonly used as a garnish or decorative finishing element for another.
-
B.
traditionalAccompaniment
Indicates that one entity is customarily or culturally served, used, or presented together with another as its traditional accompaniment.
-
C.
traditionalFilling
Indicates that something is filled using a customary or historically established type of filling associated with a particular practice, item, or cuisine.
-
D.
traditionallyServed
Indicates that one entity is customarily or conventionally presented, offered, or consumed together with another entity.
-
E.
traditionalGreen
Indicates that something adheres to or embodies a customary or historically established form of the color green.
- 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_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. |
Created at: April 10, 2026, 11:52 a.m.