Triple
T13597259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kellogg Eye Center |
E324852
|
entity |
| Predicate | hasSpecialtyClinic |
P77388
|
FINISHED |
| Object | retina clinic |
—
|
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: retina clinic | Statement: [Kellogg Eye Center, hasSpecialtyClinic, retina clinic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialtyClinic Context triple: [Kellogg Eye Center, hasSpecialtyClinic, retina clinic]
-
A.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
B.
hasSpecialist
Indicates that one entity is associated with or assigned to a specialist entity that provides expert support, service, or oversight for it.
-
C.
hasSpecialistStatus
Indicates that an entity holds a recognized specialist designation or status in a particular field, role, or context.
-
D.
hasClinicalService
chosen
Indicates that an entity provides, offers, or is associated with a specific clinical service.
-
E.
supportsMedicalSpecialty
Indicates that one entity provides resources, infrastructure, or services that enable or facilitate the practice or development of a particular medical specialty.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0590558819080ccc5874a650b1e |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.