Triple
T34646879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States (various ceremony venues) |
E889721
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geographical collection of event venues |
C56584
|
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: geographical collection of event venues Context triple: [United States (various ceremony venues), instanceOf, geographical collection of event venues]
-
A.
network of concert venues
A network of concert venues is an interconnected system of performance spaces that coordinate scheduling, promotion, and resources to host live music and entertainment events across multiple locations.
-
B.
conference and events district
A conference and events district is a designated urban area concentrated with venues, facilities, and supporting services designed to host conferences, conventions, exhibitions, and large-scale events.
-
C.
sports venue collection
A sports venue collection is an organized set of multiple sports facilities or stadiums, grouped for purposes such as management, analysis, comparison, or presentation.
-
D.
entertainment venue area
chosen
An entertainment venue area is a designated space or zone that contains or surrounds facilities where people gather for leisure activities such as concerts, sports, theater, or other performances and events.
-
E.
festival venue
A festival venue is a designated location equipped with the infrastructure, amenities, and spatial layout necessary to host large-scale, often multi-day cultural, musical, or artistic events for public audiences.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:04 a.m.