Triple
T13535848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magna Charta Universitatum |
E323257
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | higher education policy document |
C3419
|
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 document Context triple: [Magna Charta Universitatum, instanceOf, higher education policy document]
-
A.
education policy framework
chosen
An education policy framework is a structured set of principles, goals, and guidelines that shapes how educational systems are organized, governed, funded, and evaluated to achieve desired learning and equity outcomes.
-
B.
higher education system segment
A higher education system segment is a distinct subset of institutions, programs, or stakeholders within the broader higher education landscape that share common characteristics, functions, or target populations.
-
C.
higher education scholar
A higher education scholar is an academic expert who studies, analyzes, and advances knowledge about postsecondary institutions, policies, practices, and student experiences.
-
D.
state education policy document
A state education policy document is an official written directive issued by a state authority that outlines goals, standards, regulations, and implementation guidelines for the operation and improvement of the public education system within that state.
-
E.
higher education agency
A higher education agency is an organization responsible for overseeing, coordinating, regulating, or supporting postsecondary institutions and policies within a specific jurisdiction or sector.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:44 p.m.