Triple
T14124226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Ilorin |
E339984
|
entity |
| Predicate | hasRectorOrViceChancellor |
P142
|
FINISHED |
| Object | Vice-Chancellor |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Vice-Chancellor | Statement: [University of Ilorin, hasRectorOrViceChancellor, Vice-Chancellor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRectorOrViceChancellor Context triple: [University of Ilorin, hasRectorOrViceChancellor, Vice-Chancellor]
-
A.
hasViceChancellor
chosen
Indicates that one entity serves as the vice chancellor of another entity.
-
B.
principalAndViceChancellor
Indicates that one entity holds the role of principal while also serving as the vice chancellor of an institution in relation to another entity.
-
C.
hasRectorate
Indicates that an institution or organization possesses or is governed by a rectorate (a rector’s administrative office or governing body).
-
D.
servedAsViceChancellorUntil
Indicates that an individual held the position of vice chancellor up to a specified end date or time period.
-
E.
hasProvost
Indicates that an institution or organization has a specific person serving in the role of provost.
- F. None of above.
Provenance (3 batches)
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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6095548881908a9e66adccca92d2 |
completed | April 14, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.