Triple
T27725668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Plains |
E699087
|
entity |
| Predicate | hasTreatmentType |
P122242
|
FINISHED |
| Object | primary treatment |
—
|
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: primary treatment | Statement: [Blue Plains, hasTreatmentType, primary treatment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTreatmentType Context triple: [Blue Plains, hasTreatmentType, primary treatment]
-
A.
hasReceivedTreatmentFor
Indicates that an entity has undergone or been given a treatment in relation to a specified condition, issue, or problem.
-
B.
hasTreatmentAspect
Indicates that something includes, involves, or is characterized by a particular aspect or component of a treatment.
-
C.
hasCommonTreatment
Indicates that two or more entities share at least one treatment method or therapeutic approach in common.
-
D.
hasTreatmentConsideration
Indicates that a particular factor, condition, or option should be taken into account when planning, selecting, or managing a treatment.
-
E.
treatmentType
chosen
Indicates the specific kind or category of treatment applied or prescribed in relation to an entity or condition.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: April 27, 2026, 3:09 p.m.