Triple
T10316085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pterois volitans |
E242017
|
entity |
| Predicate | treatmentForSting |
P4714
|
FINISHED |
| Object | hot water immersion |
—
|
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: hot water immersion | Statement: [Pterois volitans, treatmentForSting, hot water immersion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatmentForSting Context triple: [Pterois volitans, treatmentForSting, hot water immersion]
-
A.
venomAllergenicToHumans
Indicates that a particular venom causes allergic reactions or hypersensitivity responses in humans.
-
B.
hasStingingHairs
Indicates that an entity possesses hairs capable of delivering a sting or irritation upon contact.
-
C.
treatment
chosen
Indicates that one entity is used as a medical or therapeutic intervention to address, manage, or cure a condition affecting another entity.
-
D.
knownForTreatmentOf
Indicates that an entity is recognized or notable for providing treatment or medical care for a particular condition, disease, or type of patient.
-
E.
stingingHairsContain
Indicates that the stinging hairs of an organism or structure contain a specified substance or component.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f4f354819080b4ed4bc61bdff6 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:49 a.m.