Triple
T5487612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | national rectors’ conferences |
E123621
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | higher education coordination 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 coordination body Context triple: [national rectors’ conferences, instanceOf, higher education coordination body]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
university governing body
A university governing body is a formal group of appointed or elected individuals responsible for setting the institution’s strategic direction, overseeing its policies and finances, and ensuring accountability and compliance with legal and educational standards.
-
E.
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.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:10 p.m.