Triple
T23156031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Courts of the University of Cambridge |
E578439
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic quadrangles |
C47315
|
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: historic quadrangles Context triple: [Courts of the University of Cambridge, instanceOf, historic quadrangles]
-
A.
historic intersection
A historic intersection is a crossroads or junction that has significant cultural, social, or political importance due to notable events, architecture, or long-standing community activity that occurred or developed there.
-
B.
historical district
A historical district is a geographically defined area recognized for its concentration of buildings, structures, and sites that collectively reflect significant cultural, architectural, or historical heritage.
-
C.
historic city square
A historic city square is a central public open space in a town or city, typically surrounded by significant buildings and monuments, that has served as a focal point for social, political, and commercial activities over time.
-
D.
historic district feature
A historic district feature is a physical element, structure, or landscape component within a designated historic area that contributes to its historical, architectural, or cultural significance.
-
E.
historic civic space
A historic civic space is a publicly accessible area of enduring cultural, political, or social significance where communities have traditionally gathered for collective activities, events, and civic life.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 4:01 p.m.