Triple
T17209957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semaeostomeae |
E417700
|
entity |
| Predicate | hasStingingCapability |
P52186
|
FINISHED |
| Object | can sting humans |
—
|
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: can sting humans | Statement: [Semaeostomeae, hasStingingCapability, can sting humans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStingingCapability Context triple: [Semaeostomeae, hasStingingCapability, can sting humans]
-
A.
hasStinger
Indicates that an entity possesses a stinger as a physical feature.
-
B.
hasStingingHairs
Indicates that an entity possesses hairs capable of delivering a sting or irritation upon contact.
-
C.
containsVenomousSpecies
Indicates that the referenced entity includes within it one or more species that are venomous.
-
D.
hasCnidocytes
chosen
Indicates that an organism possesses cnidocytes, the specialized stinging cells characteristic of cnidarians.
-
E.
venomDeliverySystem
Indicates the mechanism or method by which venom is produced, stored, and transferred from one organism to another.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dc4792081909443df7937768ede |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.