Triple
T6741652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rectoría General |
E154096
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university administrative body |
C1500
|
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: university administrative body Context triple: [Rectoría General, instanceOf, university administrative body]
-
A.
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.
-
B.
university administrative unit
chosen
A university administrative unit is an organizational division within a university responsible for managing specific operational, academic, or support functions to ensure the institution runs effectively and complies with policies and regulations.
-
C.
collegiate body
A collegiate body is a formal group of individuals who collectively deliberate, decide, or govern on matters within a shared institutional or organizational authority.
-
D.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
E.
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.
- 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:10 p.m.