Triple
T20497521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Tower |
E502912
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | landmark in Munich |
C24949
|
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 in Munich Context triple: [Chinese Tower, instanceOf, landmark in Munich]
-
A.
building in Munich
chosen
A building in Munich is a constructed structure within the city of Munich, Germany, serving residential, commercial, cultural, or administrative purposes and reflecting the region’s architectural styles and urban context.
-
B.
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.
-
C.
landmark in Nuremberg
A landmark in Nuremberg is a notable physical site or structure within the city—such as a historic building, monument, square, or cultural institution—that holds significant historical, architectural, or cultural importance and serves as a recognizable point of reference for residents and visitors.
-
D.
Landmark in Meissen
A "Landmark in Meissen" represents any notable, historically or culturally significant site, structure, or natural feature within the city of Meissen that serves as a recognizable point of reference or attraction.
-
E.
landmark of Frankfurt am Main
A landmark of Frankfurt am Main is a prominent, widely recognized site or structure within the city that holds cultural, historical, architectural, or symbolic significance and serves as a key point of orientation or identity for residents and visitors.
- 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_69e0b4b0373881909dd3e9387f82eab4 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:35 a.m.