Triple
T34455128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deventer koek |
E884481
|
entity |
| Predicate | isOftenEatenWith |
P148210
|
FINISHED |
| Object | butter |
—
|
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: butter | Statement: [Deventer koek, isOftenEatenWith, butter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenEatenWith Context triple: [Deventer koek, isOftenEatenWith, butter]
-
A.
isTypicallyEatenWith
chosen
Indicates that one item is commonly consumed together with another as part of the same eating occasion or dish.
-
B.
isOftenEaten
Indicates that the subject is frequently consumed as food by some agent or group.
-
C.
servedTogetherWith
Indicates that two entities were provided, offered, or used at the same time as part of the same service, event, or context.
-
D.
isTypicallyConsumedAs
Indicates that one entity is normally or customarily eaten or drunk in the form of another entity.
-
E.
typicallyEatenAt
Indicates that something is most commonly or customarily eaten during a particular time, event, or context.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71976c49c8190943046a0ff8950cb |
completed | May 3, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.