Triple
T24042374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brasserie de Schiltigheim |
E595418
|
entity |
| Predicate | partOfLocalCulture |
P145610
|
FINISHED |
| Object | Alsatian beer culture |
—
|
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: Alsatian beer culture | Statement: [Brasserie de Schiltigheim, partOfLocalCulture, Alsatian beer culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfLocalCulture Context triple: [Brasserie de Schiltigheim, partOfLocalCulture, Alsatian beer culture]
-
A.
hasLocalCult
Indicates that an entity is associated with a cult or worship practice that is specific to a particular locality or region.
-
B.
hasCulturalSignificanceFor
Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
-
C.
isPartOfCulturalDomain
chosen
Indicates that something belongs to, falls within, or is associated with a particular cultural sphere, tradition, or domain.
-
D.
aboutCulture
Indicates that something concerns, references, or is related to a particular culture, its practices, values, or expressions.
-
E.
hasCulturalCommunity
Indicates that an entity is associated with, belongs to, or is part of a specific cultural community.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8da38548190b2cc04ce7960ef9c |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:58 p.m.