Triple
T31792060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statler Hotel |
E811496
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university-owned hotel |
C57120
|
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: university-owned hotel Context triple: [Statler Hotel, instanceOf, university-owned hotel]
-
A.
university-affiliated property
chosen
A university-affiliated property is any real estate, facility, or land parcel that is owned, leased, managed, or formally controlled by a university or its associated entities for academic, administrative, research, residential, or auxiliary purposes.
-
B.
university-owned airport
A university-owned airport is an aviation facility operated and managed by a higher education institution, primarily supporting its academic, research, training, and transportation needs while potentially serving the surrounding community.
-
C.
university faculty residence
A university faculty residence is a housing facility provided by a university for its academic staff, often located on or near campus to support convenient living, community building, and institutional engagement.
-
D.
Residential university
A residential university is an institution of higher education where students live on or near campus in university-provided housing, integrating academic, social, and extracurricular life within a cohesive community environment.
-
E.
university dormitory
A university dormitory is a residential building on or near a campus that provides students with shared or individual living spaces and basic amenities during their studies.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:39 p.m.