Triple
T14201955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuskegee syphilis study |
E351984
|
entity |
| Predicate | standardTreatmentAvailableBy |
P113187
|
FINISHED |
| Object | mid-1940s |
—
|
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: mid-1940s | Statement: [Tuskegee syphilis study, standardTreatmentAvailableBy, mid-1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardTreatmentAvailableBy Context triple: [Tuskegee syphilis study, standardTreatmentAvailableBy, mid-1940s]
-
A.
hasCommonTreatment
Indicates that two or more entities share at least one treatment method or therapeutic approach in common.
-
B.
supportsTreatmentType
Indicates that one entity is capable of providing, handling, or is compatible with a specified type of treatment.
-
C.
hasReceivedTreatmentFor
Indicates that an entity has undergone or been given a treatment in relation to a specified condition, issue, or problem.
-
D.
hasTreatmentConsideration
Indicates that a particular factor, condition, or option should be taken into account when planning, selecting, or managing a treatment.
-
E.
usesTreatment
Indicates that one entity applies or employs a particular treatment or therapeutic method on or for another entity.
- F. None of above. chosen
Provenance (4 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61f589a08190b71ad4e69d92ffd0 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:05 a.m.