Triple
T2763056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Campus (American University) |
E61269
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | campus expansion project |
C2938
|
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: campus expansion project Context triple: [East Campus (American University), instanceOf, campus expansion project]
-
A.
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.
-
B.
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.
-
C.
multi-campus university
A multi-campus university is an institution of higher education that operates multiple geographically separate campuses under a single administrative and academic governance structure.
-
D.
multi-campus university structure
A multi-campus university structure is an organizational framework in which a single university operates multiple geographically dispersed campuses that share governance, academic standards, and resources while serving distinct local communities and programmatic needs.
-
E.
infrastructure project
chosen
An infrastructure project is a large-scale, organized effort to plan, design, and construct foundational physical systems—such as transportation, utilities, and public facilities—that support a community’s or region’s economic and social activities.
- 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_69ab4b7bab6c8190a5c2efef19a8ef34 |
completed | March 6, 2026, 9:47 p.m. |
Created at: March 6, 2026, 9:57 p.m.