Triple
T616117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto Metropolitan University |
E14407
|
entity |
| Predicate | hasAdministrativeStaff |
P478
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Toronto Metropolitan University, hasAdministrativeStaff, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdministrativeStaff Context triple: [Toronto Metropolitan University, hasAdministrativeStaff, yes]
-
A.
hasAdministrativeUnit
Indicates that one entity possesses, contains, or is associated with another entity that functions as its administrative subdivision or governing unit.
-
B.
hasAcademicStaff
Indicates that an institution or organization employs or is associated with one or more academic staff members.
-
C.
administeredBy
Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
-
D.
staffIncluded
chosen
Indicates that staff members are included or provided as part of the associated entity, service, or arrangement.
-
E.
hasCountyAdministrator
Indicates that an entity is administered or overseen by a specific county administrator.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e22f3688190a512bec3f0347814 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfbcbf88190a854921dc531eba8 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.