Triple
T28164966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bönnsch |
E715000
|
entity |
| Predicate | servingTraditionSimilarTo |
P103073
|
FINISHED |
| Object | Kölsch |
—
|
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: Kölsch | Statement: [Bönnsch, servingTraditionSimilarTo, Kölsch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servingTraditionSimilarTo Context triple: [Bönnsch, servingTraditionSimilarTo, Kölsch]
-
A.
servesTradition
Indicates that one entity upholds, maintains, or performs a tradition for the benefit or continuation of that tradition.
-
B.
traditionallyServed
chosen
Indicates that one entity is customarily or conventionally presented, offered, or consumed together with another entity.
-
C.
traditionIncludes
Indicates that a particular tradition encompasses, contains, or is composed of a specified element, practice, or component.
-
D.
traditionAt
Indicates that a particular tradition is practiced, observed, or associated at a specific place or location.
-
E.
isTraditionOf
Indicates that something is a customary practice, belief, or ritual associated with or belonging to a particular group, culture, 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 10:09 p.m.