Triple
T6484000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Altdorf |
E146462
|
entity |
| Predicate | academicDisciplineTaught |
P58460
|
FINISHED |
| Object | law |
—
|
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: law | Statement: [University of Altdorf, academicDisciplineTaught, law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: academicDisciplineTaught Context triple: [University of Altdorf, academicDisciplineTaught, law]
-
A.
areTaughtIn
Indicates that certain subjects, courses, or topics are instructed or delivered within specific locations, classes, or educational settings.
-
B.
isTaughtAs
Indicates that something is presented or delivered as instructional content, typically within an educational or training context.
-
C.
housesAcademicDiscipline
chosen
Indicates that an entity serves as the location or institutional home where a particular academic discipline is based, organized, or conducted.
-
D.
taughtAs
Indicates that one entity served as a teacher or instructor for another entity in an educational or training context.
-
E.
scopeOfTeaching
Indicates the range, subjects, or areas that a teaching activity, role, or responsibility covers.
- 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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a6de31c81909dd99d105f5bb4c2 |
completed | March 22, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:52 p.m.