Triple
T3002114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna University of Technology |
E81810
|
entity |
| Predicate | hasRectorate |
P44971
|
FINISHED |
| Object | Rector and Vice-Rectors |
—
|
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: Rector and Vice-Rectors | Statement: [Vienna University of Technology, hasRectorate, Rector and Vice-Rectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRectorate Context triple: [Vienna University of Technology, hasRectorate, Rector and Vice-Rectors]
-
A.
hasRectorateBuilding
Indicates that an institution possesses or is associated with a specific building that houses its rectorate (central administrative leadership).
-
B.
rectorOrPresident
Indicates that one entity serves as the rector or president (i.e., the chief executive or head) of another entity, typically an institution such as a university.
-
C.
hasProvost
Indicates that an institution or organization has a specific person serving in the role of provost.
-
D.
hasChancellor
Indicates that an entity holds the position or role of chancellor for another entity.
-
E.
hasViceChancellor
Indicates that one entity serves as the vice chancellor of another entity.
- F. None of above. chosen
Provenance (4 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a11b4bc81909ce06121361b4e0f |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 2:59 p.m.