Triple
T1169839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diagnostic Radiology Residency |
E24888
|
entity |
| Predicate | includesAssessmentBy |
P1340
|
FINISHED |
| Object | clinical evaluations |
—
|
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: clinical evaluations | Statement: [Diagnostic Radiology Residency, includesAssessmentBy, clinical evaluations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesAssessmentBy Context triple: [Diagnostic Radiology Residency, includesAssessmentBy, clinical evaluations]
-
A.
assessedBy
chosen
Indicates that an entity has been evaluated, examined, or judged by another entity (typically an agent or authority).
-
B.
assessmentMethod
Indicates the method or procedure used to evaluate, measure, or judge something.
-
C.
languageOfAssessment
Indicates that a specified language is used as the medium of assessment (e.g., for tests, evaluations, or examinations) for a given entity.
-
D.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
E.
includesClause
Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bce821b481908bc278a3fa7973f4 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5656948190b0b1d5446ad06005 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.