Triple
T14201956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuskegee syphilis study |
E351984
|
entity |
| Predicate | continuedAfterStandardTreatmentAvailable |
P95922
|
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: [Tuskegee syphilis study, continuedAfterStandardTreatmentAvailable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedAfterStandardTreatmentAvailable Context triple: [Tuskegee syphilis study, continuedAfterStandardTreatmentAvailable, true]
-
A.
subsequentTreatment
Indicates that one treatment occurs after and in response to a prior treatment or medical event.
-
B.
hasSubsequentTreatment
Indicates that one treatment occurs after and in continuation of another treatment in a temporal sequence.
-
C.
continuedThrough
chosen
Indicates that an event, state, or process persisted without interruption across or beyond a specified point, period, or boundary.
-
D.
continuesOn
Indicates that an action, process, or state persists or carries forward beyond a given point, without interruption or termination.
-
E.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by 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_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. |
Created at: April 10, 2026, 1:05 a.m.