Triple
T4307904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fresno Convention & Entertainment Center |
E94000
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | convention center complex |
C725
|
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 complex Context triple: [Fresno Convention & Entertainment Center, instanceOf, convention center complex]
-
A.
convention center
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.
entertainment complex
chosen
An entertainment complex is a large, multi-purpose facility that combines various leisure, recreational, and cultural attractions—such as cinemas, theaters, restaurants, gaming areas, and event spaces—within a single integrated venue.
-
D.
museum building complex
A museum building complex is a coordinated group of structures and spaces designed to collect, preserve, exhibit, and interpret cultural, historical, artistic, or scientific artifacts for public education and enjoyment.
-
E.
multi-purpose event venue
A multi-purpose event venue is a flexible space designed to accommodate a wide range of gatherings—such as conferences, concerts, weddings, and exhibitions—by offering adaptable layouts, technical infrastructure, and support services.
- 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
Created at: March 12, 2026, 11:11 p.m.