Triple
T19592560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Café am Neuen See |
E470271
|
entity |
| Predicate | outdoorAreaType |
P84779
|
FINISHED |
| Object | beer garden terrace |
—
|
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: beer garden terrace | Statement: [Café am Neuen See, outdoorAreaType, beer garden terrace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outdoorAreaType Context triple: [Café am Neuen See, outdoorAreaType, beer garden terrace]
-
A.
parkAreaType
Indicates the classification of a park’s area according to its designated type or functional category.
-
B.
outdoorVenue
Indicates that an event, activity, or gathering takes place at a location situated outdoors rather than inside a building or enclosed structure.
-
C.
hasOutdoorSpaceType
chosen
Indicates the specific kind of outdoor area associated with an entity, such as a balcony, terrace, garden, or patio.
-
D.
isRecreationalArea
Indicates that a place or space is designated and used primarily for leisure, relaxation, or recreational activities.
-
E.
arenaType
Indicates the specific kind or category of arena associated with an entity or event.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64057460c8190962e2e58f06b3985 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.