Triple
T9573726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salt Lake 2002 Olympic venues network |
E230990
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Olympic venues network |
C8880
|
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: Olympic venues network Context triple: [Salt Lake 2002 Olympic venues network, instanceOf, Olympic venues network]
-
A.
Olympic competition venue area
An Olympic competition venue area is a designated, secure space that includes the field of play and its immediate surroundings where official Olympic events are conducted according to sport-specific standards.
-
B.
sports venue collection
chosen
A sports venue collection is an organized set of multiple sports facilities or stadiums, grouped for purposes such as management, analysis, comparison, or presentation.
-
C.
athletes' village
An athletes' village is a dedicated residential complex that houses competitors and team officials during a multi-sport event, providing accommodation, dining, training, medical, and recreational facilities in a secure, centralized environment.
-
D.
Olympic legacy organization
An Olympic legacy organization is an entity dedicated to preserving, managing, and enhancing the long-term social, economic, and environmental benefits of hosting the Olympic Games for the host city, region, and nation.
-
E.
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.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:05 p.m.