Triple
T30975196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpirsbach |
E789210
|
entity |
| Predicate | beerBrandOrigin |
P170868
|
FINISHED |
| Object | Alpirsbacher Klosterbräu |
—
|
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: Alpirsbacher Klosterbräu | Statement: [Alpirsbach, beerBrandOrigin, Alpirsbacher Klosterbräu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beerBrandOrigin Context triple: [Alpirsbach, beerBrandOrigin, Alpirsbacher Klosterbräu]
-
A.
beerBrand
Indicates that one entity is a brand designation for a particular type or product of beer associated with the other entity.
-
B.
beerStyleOrigin
Indicates the place or region where a particular beer style was originally developed or first became established.
-
C.
beerBrewedBy
Indicates that a particular beer is produced or created by a specific brewer, brewery, or brewing entity.
-
D.
bottledBy
Indicates that one entity is responsible for placing another entity into bottles or containers for packaging or distribution.
-
E.
beerStyleRegion
Indicates the geographic region or origin associated with a particular beer style.
- F. None of above. chosen
Provenance (4 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:55 p.m.