Triple
T3839153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innenstadt (Frankfurt am Main) |
E93408
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Stadtteil von Frankfurt am Main |
C14506
|
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: Stadtteil von Frankfurt am Main Context triple: [Innenstadt (Frankfurt am Main), instanceOf, Stadtteil von Frankfurt am Main]
-
A.
Stadtbezirk of Hanover
A Stadtbezirk of Hanover is an administrative borough within the city that groups several neighborhoods for local governance, planning, and public services.
-
B.
independent city in Germany
An independent city in Germany is a municipality that holds the status of both a city and a district (kreisfreie Stadt), administering local and district-level responsibilities without being part of a surrounding rural district.
-
C.
region of Germany
A region of Germany is a geographically and culturally distinct area within the country, often defined by historical boundaries, administrative divisions, or shared economic and social characteristics.
-
D.
sector of Berlin
A sector of Berlin is a geographically defined administrative or historical subdivision of the city, often reflecting political, economic, or cultural distinctions within the urban area.
-
E.
town in Germany
A town in Germany is a moderately sized, legally defined urban municipality that serves as a local administrative, economic, and cultural center within the German federal system.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
Created at: March 9, 2026, 3:18 p.m.