Triple
T32317970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KUL |
E825691
|
entity |
| Predicate | foundingRector |
P25902
|
FINISHED |
| Object | Idzi Radziszewski |
—
|
NE NERFINISHED |
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: Idzi Radziszewski | Statement: [KUL, foundingRector, Idzi Radziszewski]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingRector Context triple: [KUL, foundingRector, Idzi Radziszewski]
-
A.
foundingChancellor
Indicates that a person served as the first (original) chancellor at the founding of an institution or organization.
-
B.
rectorOrPresident
chosen
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.
foundingViceChancellor
Indicates that a person served as the first (founding) vice chancellor of an institution or organization.
-
D.
foundingDirector
Indicates that one entity is the original director who established or helped establish the other entity (such as an organization, project, or institution).
-
E.
hasHistoricalFigureAsRector
Indicates that an institution has, at some point in its history, had a notable historical figure serve in the role of rector.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 1, 2026, 12:46 a.m.