Triple
T755095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University Hospital Zurich |
E15535
|
entity |
| Predicate | conductsClinicalResearch |
P5263
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [University Hospital Zurich, conductsClinicalResearch, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conductsClinicalResearch Context triple: [University Hospital Zurich, conductsClinicalResearch, true]
-
A.
conductsResearchAt
chosen
Indicates that a subject carries out research activities at a specified institution, organization, or location.
-
B.
operatesResearchCenter
Indicates that an entity manages and runs the activities of a research center.
-
C.
hasResearchStatus
Indicates that an entity holds a particular stage or condition within a research process, such as planned, in progress, completed, or published.
-
D.
researchArm
Indicates that an entity is a specific study group or treatment arm within a research or clinical trial design.
-
E.
supervisedDoctoralResearchOf
Indicates that one entity served as the doctoral research supervisor of another entity.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66820548190b373deb117187c2c |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a501c4cc81908de6d63e3d4f60d7 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.