Triple
T33389771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lionfishes |
E855012
|
entity |
| Predicate | stingTreatment |
P177015
|
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: [lionfishes, stingTreatment, hot water immersion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stingTreatment Context triple: [lionfishes, stingTreatment, hot water immersion]
-
A.
stingSymptoms
Indicates that an entity experiences symptoms as a result of being stung by another entity.
-
B.
sting
Indicates inflicting a sharp, piercing pain or wound, typically by means of a pointed body part or object.
-
C.
stingPresent
Indicates that a stinging organ or structure is present on the 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.
treats
Indicates that one entity provides medical care or therapeutic intervention to 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f814fcf48190ae4504154d1b2c05 |
completed | May 3, 2026, 7:24 a.m. |
Created at: May 1, 2026, 1:35 a.m.