Triple
T16246443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paulskirche |
E394382
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | landmark of Frankfurt am Main |
C37170
|
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: landmark of Frankfurt am Main Context triple: [Paulskirche, instanceOf, landmark of Frankfurt am Main]
-
A.
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.
-
B.
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.
-
C.
Bismarck tower
A Bismarck tower is a monumental structure, typically built on elevated ground in the late 19th and early 20th centuries across Germany and former German territories, commemorating Chancellor Otto von Bismarck and often serving as a lookout or observation tower.
-
D.
landmark in Lübeck
A landmark in Lübeck is a notable physical site, building, or monument within the city that holds historical, cultural, architectural, or social significance and serves as a recognizable point of reference for residents and visitors.
-
E.
Nuremberg U-Bahn station
A Nuremberg U-Bahn station is an underground or partially underground public transit facility in Nuremberg, Germany, where passengers access, board, and transfer between Nuremberg U-Bahn trains and related services.
- F. None of above. chosen
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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:04 a.m.