Triple
T33336597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knuffingen Airport |
E853552
|
entity |
| Predicate | openedAsExhibitAt |
P192235
|
FINISHED |
| Object | Miniatur Wunderland |
—
|
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: Miniatur Wunderland | Statement: [Knuffingen Airport, openedAsExhibitAt, Miniatur Wunderland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsExhibitAt Context triple: [Knuffingen Airport, openedAsExhibitAt, Miniatur Wunderland]
-
A.
openedAsMuseumIn
Indicates that a place or building began operating as a museum in a specified year or at a specified time.
-
B.
propExhibitedAt
Indicates that a property or characteristic is displayed or manifested at a particular place, time, or context.
-
C.
exhibitedDuring
Indicates that something was presented, displayed, or shown over the course of a specified time period or event.
-
D.
exhibitedFor
Indicates that something is displayed, presented, or shown for the benefit, use, or consideration of a particular audience, purpose, or entity.
-
E.
exhibitedBeforeInstallationAt
Indicates that an item was publicly displayed or shown prior to being installed at a particular location or in a specific context.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69fd026757a081909911a59a78652709 |
completed | May 7, 2026, 9:21 p.m. |
Created at: May 1, 2026, 1:34 a.m.