Triple
T27491361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shakespearean theatre district of Bankside |
E693892
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic theatre district |
C24185
|
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 theatre district Context triple: [Shakespearean theatre district of Bankside, instanceOf, historic theatre district]
-
A.
historic theater
A historic theater is a long-standing performance venue of architectural or cultural significance that has hosted artistic events across generations and often reflects the social and artistic heritage of its era.
-
B.
historical district
chosen
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 market district
A historic market district is a preserved urban area where traditional marketplaces, architecture, and cultural practices converge to reflect the commercial and social life of a community across 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 city quarter
A historic city quarter is an urban area characterized by preserved architecture, street patterns, and cultural landmarks that reflect the social, economic, and architectural history of a particular period.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:05 p.m.