Triple
T38317806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Ross Jennings |
E1033873
|
entity |
| Predicate | replacesAsTownDoctor |
P197759
|
FINISHED |
| Object | Dr. Sam Metcalf |
—
|
NE NERFINISHED |
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: Dr. Sam Metcalf | Statement: [Dr. Ross Jennings, replacesAsTownDoctor, Dr. Sam Metcalf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesAsTownDoctor Context triple: [Dr. Ross Jennings, replacesAsTownDoctor, Dr. Sam Metcalf]
-
A.
changesMedicalPractice
Indicates that one entity causes or leads to a modification in another entity’s medical practices, procedures, or clinical behavior.
-
B.
replacedAdministrationOf
chosen
Indicates that one entity has taken over and superseded the administrative control or management responsibilities previously held by another entity.
-
C.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
D.
doctorNumber
Indicates the unique identifying number assigned to a doctor in the context of a relationship or record.
-
E.
medicalPractice
Indicates a relationship where an entity engages in or carries out the professional provision of medical care or services.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
Created at: May 3, 2026, 4:30 p.m.