Triple
T11272919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hochschule Bonn-Rhein-Sieg campus Bad Honnef (historical) |
E266857
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former university campus |
C18065
|
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: former university campus Context triple: [Hochschule Bonn-Rhein-Sieg campus Bad Honnef (historical), instanceOf, former university campus]
-
A.
former campus site
chosen
A former campus site is a location that once hosted an educational institution’s campus but has since been repurposed, abandoned, or redeveloped for other uses.
-
B.
university satellite campus
A university satellite campus is a geographically separate branch of a main university that offers selected academic programs and services to extend access to higher education in a different location.
-
C.
university campus area
A university campus area is the designated physical environment of a university, encompassing academic buildings, student housing, recreational facilities, green spaces, and supporting infrastructure where educational and social activities occur.
-
D.
regional college campus
A regional college campus is a localized branch of a larger higher-education institution that provides academic programs, student services, and community engagement tailored to the needs of a specific geographic area.
-
E.
former campus of Durham University
A former campus of Durham University is a previously used site or collection of buildings that once hosted the university’s academic, residential, or administrative activities but is no longer part of its active estate.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:31 p.m.