Triple
T3825991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USZ |
E88690
|
entity |
| Predicate | hasAcademicStatus |
P6978
|
FINISHED |
| Object | university-affiliated hospital |
—
|
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-affiliated hospital | Statement: [USZ, hasAcademicStatus, university-affiliated hospital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAcademicStatus Context triple: [USZ, hasAcademicStatus, university-affiliated hospital]
-
A.
academicStatus
chosen
Indicates the educational or scholarly standing or level an entity holds within an academic context.
-
B.
hasAcademicComponent
Indicates that something includes, involves, or is associated with an academic or educational element as part of its structure or content.
-
C.
hasAcademicRank
Indicates that an entity holds a specific academic rank or title within an educational or research institution.
-
D.
hasAcademicBackgroundIn
Indicates that an entity possesses formal education, training, or scholarly experience in a specified academic field or discipline.
-
E.
hasAcademicFunction
Indicates that an entity serves a specific academic role, duty, or function within an educational or scholarly context.
- 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8459f881908a2c91bb07e381ef |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.