Triple
T27787138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meropidae |
E700991
|
entity |
| Predicate | venomHandling |
P163353
|
FINISHED |
| Object | remove stings of bees and wasps before eating |
—
|
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: remove stings of bees and wasps before eating | Statement: [Meropidae, venomHandling, remove stings of bees and wasps before eating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venomHandling Context triple: [Meropidae, venomHandling, remove stings of bees and wasps before eating]
-
A.
venomDeliverySystem
Indicates the mechanism or method by which venom is produced, stored, and transferred from one organism to another.
-
B.
venomPresentIn
Indicates that venom is contained within, or occurs as a component of, a specified entity or substance.
-
C.
venomAllergenicToHumans
Indicates that a particular venom causes allergic reactions or hypersensitivity responses in humans.
-
D.
venomPotency
Indicates the degree of strength or toxicity of an entity’s venom in affecting another entity.
-
E.
venomous
Indicates that an organism possesses venom and can inject or deliver it to another organism, typically as a means of defense or predation.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637d2e5e08190bc1708336a4fbfc5 |
completed | May 2, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 5:25 p.m.