Triple
T6992935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanderring campus |
E162127
|
entity |
| Predicate | hasStudentAccess |
P45383
|
FINISHED |
| Object | University of Würzburg students |
—
|
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: University of Würzburg students | Statement: [Sanderring campus, hasStudentAccess, University of Würzburg students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudentAccess Context triple: [Sanderring campus, hasStudentAccess, University of Würzburg students]
-
A.
hasSchoolsAccess
chosen
Indicates that one entity has permission or the ability to access schools or school-related resources associated with another entity.
-
B.
hasStudentEnrollment
Indicates that a person or entity is enrolled as a student in a particular course, program, or educational institution.
-
C.
hasStudentCategory
Indicates that an entity is classified under a specific category or type of student.
-
D.
hasStudentServices
Indicates that an entity provides or is associated with student support services for another entity or group.
-
E.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc30fdc81909244d83c8178755c |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.