Triple
T9827168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Museum für Moderne Kunst Frankfurt |
E238685
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | museum in Frankfurt am Main |
C15150
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: museum in Frankfurt am Main Context triple: [Museum für Moderne Kunst Frankfurt, instanceOf, museum in Frankfurt am Main]
-
A.
museum in Munich
A museum in Munich is a cultural institution located within the city that collects, preserves, researches, and exhibits artworks, artifacts, or historical objects for public education and enjoyment.
-
B.
museum building in Germany
chosen
A museum building in Germany is a purpose-built or repurposed structure located within German territory that houses, preserves, and publicly exhibits collections of cultural, historical, artistic, or scientific significance.
-
C.
Frankfurt U-Bahn station
A Frankfurt U-Bahn station is an underground or surface-level transit facility in Frankfurt am Main where passengers access, board, and transfer between urban metro trains on the city's U-Bahn network.
-
D.
Berlin Wall museum
A Berlin Wall museum is a cultural institution dedicated to preserving, exhibiting, and interpreting artifacts, stories, and historical context related to the Berlin Wall and its impact on Germany and the world.
-
E.
cultural heritage monument in Berlin
A cultural heritage monument in Berlin is a legally protected building, site, or structure recognized for its historical, architectural, or cultural significance within the city’s heritage conservation framework.
- F. None of above.
Provenance (1 batch)
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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:32 p.m.