Triple
T37028302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruby (gemstone) |
E916415
|
entity |
| Predicate | commonTreatment |
P199303
|
FINISHED |
| Object | heat 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: heat treatment | Statement: [Ruby (gemstone), commonTreatment, heat treatment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonTreatment Context triple: [Ruby (gemstone), commonTreatment, heat treatment]
-
A.
treats
Indicates that one entity provides medical care or therapeutic intervention to another entity.
-
B.
possibleTreatment
Indicates that one entity can serve as a potential method or option for treating, alleviating, or managing another entity (typically a condition or disease).
-
C.
hasCommonTreatment
Indicates that two or more entities share at least one treatment method or therapeutic approach in common.
-
D.
usesTreatment
Indicates that one entity applies or employs a particular treatment or therapeutic method on or for another entity.
-
E.
knownForTreatmentOf
Indicates that an entity is recognized or notable for providing treatment or medical care for a particular condition, disease, or type of patient.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
| PDg | Predicate description generation | batch_69ff2d21f0a48190ad2ef5901cb07d93 |
completed | May 9, 2026, 12:48 p.m. |
Created at: May 3, 2026, 4:14 p.m.