Triple
T33389768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lionfishes |
E855012
|
entity |
| Predicate | stingSymptoms |
P176846
|
FINISHED |
| Object | intense pain |
—
|
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: intense pain | Statement: [lionfishes, stingSymptoms, intense pain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stingSymptoms Context triple: [lionfishes, stingSymptoms, intense pain]
-
A.
viewsSymptoms
Indicates that one entity observes or examines the symptoms associated with another entity.
-
B.
symptomAssociatedWithInfection
Indicates that a particular symptom is linked to, or commonly occurs as a result of, a specific infection.
-
C.
isUsedForSymptom
Indicates that something (such as a treatment, medication, or intervention) is employed to address, alleviate, or manage a particular symptom.
-
D.
symptom
Indicates that a particular condition, disease, or problem manifests through a specific observable sign or complaint.
-
E.
hasPossibleSymptom
Indicates that an entity (such as a condition or disease) may be associated with a particular symptom that can potentially occur.
- 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_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6f37f36ac8190b1bff8711d6771cb |
completed | May 3, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:35 a.m.