Triple
T8125063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pepper Thai Cookbook |
E189704
|
entity |
| Predicate | notableRecipe |
P79219
|
FINISHED |
| Object | pad thai |
—
|
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: pad thai | Statement: [The Pepper Thai Cookbook, notableRecipe, pad thai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRecipe Context triple: [The Pepper Thai Cookbook, notableRecipe, pad thai]
-
A.
knownForDish
chosen
Indicates that an entity is recognized or notable for preparing, serving, or being associated with a particular dish.
-
B.
notableMeatProduct
Indicates that one entity is a meat-based product that is especially prominent, well-known, or significant in relation to the other entity.
-
C.
traditionalDish
Indicates that the object is a dish customarily prepared, eaten, or recognized within the subject’s cultural or regional tradition.
-
D.
usesRecipeOf
Indicates that one entity prepares or creates something by following the recipe or formula originally defined or used by another entity.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- 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_69ca82bb74848190afb1f18640632c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4c2e388190b86854f8b1765e61 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb3696379c8190a20965e59ed8f370 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:34 p.m.