Triple
T21030842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss University Conference |
E518057
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | higher education policy body |
C2463
|
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: higher education policy body Context triple: [Swiss University Conference, instanceOf, higher education policy body]
-
A.
education policy body
An education policy body is an organization or governing entity responsible for developing, overseeing, and evaluating policies and regulations that shape the structure, standards, and operation of an education system.
-
B.
higher education advisory panel
A higher education advisory panel is a group of experts and stakeholders who provide strategic guidance, recommendations, and informed perspectives to support decision-making and policy development in colleges, universities, or broader postsecondary systems.
-
C.
higher education agency
chosen
A higher education agency is an organization responsible for overseeing, coordinating, regulating, or supporting postsecondary institutions and policies within a specific jurisdiction or sector.
-
D.
higher education policy program
A higher education policy program is an academic course of study that prepares students to analyze, design, and implement policies governing colleges and universities within broader social, economic, and political contexts.
-
E.
higher education organization
A higher education organization is an institution that provides post-secondary academic or professional education, conducts research, and grants recognized degrees or certifications.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 1:55 p.m.