Triple
T2444885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clinical Practices of the University of Pennsylvania |
E53367
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | faculty practice plan |
C10948
|
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: faculty practice plan Context triple: [Clinical Practices of the University of Pennsylvania, instanceOf, faculty practice plan]
-
A.
university faculty
A university faculty is a group of academic staff and scholars within a higher education institution responsible for teaching, research, and academic governance in specific disciplines or departments.
-
B.
academic administrator
An academic administrator is a professional responsible for planning, organizing, and overseeing the non-teaching operations and policies of educational institutions to support their academic mission.
-
C.
academic leadership office
An academic leadership office is a centralized unit within an educational institution responsible for guiding strategic direction, supporting faculty and program development, and coordinating policies and initiatives that advance the institution’s academic mission.
-
D.
academic chair
An academic chair is a senior faculty position, often endowed, that provides leadership in a specific discipline through teaching, research, and service within a higher education institution.
-
E.
academic program
An academic program is a structured set of courses, requirements, and learning experiences offered by an educational institution that leads to a specific credential, such as a degree, diploma, or certificate.
- F. None of above. chosen
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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:43 p.m.