Triple
T28169499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerusalem: A Cookbook |
E715416
|
entity |
| Predicate | featuresIngredient |
P12771
|
FINISHED |
| Object | tahini |
—
|
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: tahini | Statement: [Jerusalem: A Cookbook, featuresIngredient, tahini]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresIngredient Context triple: [Jerusalem: A Cookbook, featuresIngredient, tahini]
-
A.
ingredientType
Indicates that one entity is classified as a specific type or category of ingredient in relation to another.
-
B.
usesIngredient
chosen
Indicates that one entity employs or incorporates another entity as an ingredient in its composition or creation.
-
C.
usesIngredientInfluenceFrom
Indicates that one entity incorporates or applies the influence, properties, or effects derived from a particular ingredient in its action or outcome.
-
D.
cuisineFeature
Indicates a characteristic, quality, or notable aspect that describes or distinguishes a particular cuisine.
-
E.
hasKeyIngredientAttribute
Indicates that an entity possesses a specific key ingredient as a defining attribute or component.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: April 27, 2026, 10:11 p.m.