Triple
T15718536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hope Park |
E381023
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative campus |
C16315
|
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: administrative campus Context triple: [Hope Park, instanceOf, administrative campus]
-
A.
campus
chosen
A campus is a defined area of land that houses the buildings, facilities, and open spaces of an educational institution, supporting academic, residential, and social activities.
-
B.
government campus
A government campus is a designated area comprising multiple buildings and facilities where various governmental departments and agencies are co-located to conduct administrative, legislative, or public service functions.
-
C.
academic administrative office
An academic administrative office is a centralized unit within an educational institution responsible for managing academic records, coordinating course and program logistics, supporting faculty and students with administrative processes, and ensuring compliance with institutional and regulatory policies.
-
D.
university administration building
A university administration building is a central facility on campus that houses offices and services responsible for managing the institution’s academic, financial, and operational affairs.
-
E.
university administrative unit
A university administrative unit is an organizational division within a university responsible for managing specific operational, academic, or support functions to ensure the institution runs effectively and complies with policies and regulations.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:45 a.m.