Triple
T6475286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endenich campus |
E146055
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | site of the University of Bonn |
C19885
|
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: site of the University of Bonn Context triple: [Endenich campus, instanceOf, site of the University of Bonn]
-
A.
site of Heidelberg University
The site of Heidelberg University is the physical and virtual environment encompassing its campuses, buildings, facilities, and online presence where academic, research, and administrative activities take place.
-
B.
site of Humboldt University of Berlin
The site of Humboldt University of Berlin is the physical and institutional location in Berlin where the university’s academic, administrative, and cultural activities are concentrated, including its historic buildings, campuses, and associated facilities.
-
C.
site of Chemnitz University of Technology
The site of Chemnitz University of Technology is the physical and organizational location encompassing its campuses, buildings, facilities, and infrastructure where the university’s academic, research, and administrative activities take place.
-
D.
district of Bonn
A district of Bonn is an administrative subdivision of the German city of Bonn, encompassing specific neighborhoods and local governance functions within the city's overall municipal structure.
-
E.
borough of Bonn
chosen
A borough of Bonn is an administrative subdivision of the German city of Bonn that encompasses specific neighborhoods and local governance functions within its defined geographic area.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 4:50 p.m.