Triple
T8901880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle Convention Center Summit |
E211948
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | convention center expansion project |
C3167
|
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: convention center expansion project Context triple: [Seattle Convention Center Summit, instanceOf, convention center expansion project]
-
A.
convention center
chosen
A convention center is a large, purpose-built facility designed to host conferences, trade shows, exhibitions, and other large-scale events, providing flexible meeting spaces and supporting services.
-
B.
conference center
A conference center is a large, purpose-built facility designed to host meetings, conventions, exhibitions, and other events, providing flexible spaces and supporting services for groups of various sizes.
-
C.
healthcare facility expansion program
A healthcare facility expansion program is a coordinated initiative to increase a medical institution’s capacity, services, and infrastructure to better meet current and future patient care needs.
-
D.
museum building extension
A museum building extension is an added architectural volume or wing that expands a museum’s spatial capacity, functionality, and visitor experience while integrating with or reinterpreting the existing structure.
-
E.
convention hotel
A convention hotel is a large lodging facility specifically designed to host conferences and events, featuring extensive meeting spaces, ballrooms, and business amenities alongside standard guest accommodations.
- 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:55 p.m.