Triple
T26553680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malmsey |
E671745
|
entity |
| Predicate | pairsWithFood |
P148210
|
FINISHED |
| Object | blue cheese |
—
|
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: blue cheese | Statement: [Malmsey, pairsWithFood, blue cheese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairsWithFood Context triple: [Malmsey, pairsWithFood, blue cheese]
-
A.
typicalFoodPairing
Indicates that one food item is commonly served, consumed, or matched together with another as a customary or complementary pairing.
-
B.
servedTogetherWith
Indicates that two entities were provided, offered, or used at the same time as part of the same service, event, or context.
-
C.
accompaniesTo
Indicates that one entity goes along with or escorts another entity to a specific destination or event.
-
D.
offersFoodWithCompanion
Indicates that an entity provides food to someone while accompanied by another person or companion.
-
E.
isTypicallyEatenWith
chosen
Indicates that one item is commonly consumed together with another as part of the same eating occasion or dish.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6146436408190bec22ccca6458ca8 |
completed | May 2, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 1:48 a.m.