Triple
T34455132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deventer koek |
E884481
|
entity |
| Predicate | isCommerciallyProducedIn |
P3992
|
FINISHED |
| Object | Deventer |
—
|
NE NERFINISHED |
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: Deventer | Statement: [Deventer koek, isCommerciallyProducedIn, Deventer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommerciallyProducedIn Context triple: [Deventer koek, isCommerciallyProducedIn, Deventer]
-
A.
isProducedIn
chosen
Indicates that something is created, manufactured, or generated within a particular place, context, or process.
-
B.
originallyProducedIn
Indicates that something was first created, manufactured, or brought into existence in a particular place or location.
-
C.
isProducedFrom
Indicates that something is created, generated, or derived from a specified source or input.
-
D.
isMajorProducerOf
Indicates that an entity plays a leading or highly significant role in producing or supplying a particular product, resource, or output.
-
E.
isFrequentlyProducedBy
Indicates that something is commonly or regularly generated, created, or brought about by a particular entity or source.
- 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_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 1, 2026, 2 a.m.