Triple
T8633844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | joint board of University of Amsterdam and Vrije Universiteit Amsterdam |
E204470
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint governing body |
C172
|
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: joint governing body Context triple: [joint board of University of Amsterdam and Vrije Universiteit Amsterdam, instanceOf, joint governing body]
-
A.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
B.
governing council
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
-
C.
intergovernmental legal body
An intergovernmental legal body is an organization formed by multiple governments to develop, interpret, or oversee the implementation of international legal norms, agreements, and dispute-resolution mechanisms.
-
D.
governing body members
Individuals who hold official positions within a governing body and are responsible for making, interpreting, or enforcing policies and decisions on behalf of an organization, community, or state.
-
E.
advisory body
An advisory body is a group of appointed or elected individuals that provides expert guidance, recommendations, and informed opinions to decision-makers without having formal authority to implement decisions.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.