Triple
T28496325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solenodontidae |
E721114
|
entity |
| Predicate | hasVenomDeliverySystem |
P93329
|
FINISHED |
| Object | submaxillarySalivaryGlands |
—
|
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: submaxillarySalivaryGlands | Statement: [Solenodontidae, hasVenomDeliverySystem, submaxillarySalivaryGlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVenomDeliverySystem Context triple: [Solenodontidae, hasVenomDeliverySystem, submaxillarySalivaryGlands]
-
A.
venomDeliverySystem
chosen
Indicates the mechanism or method by which venom is produced, stored, and transferred from one organism to another.
-
B.
hasStinger
Indicates that an entity possesses a stinger as a physical feature.
-
C.
venomPresentIn
Indicates that venom is contained within, or occurs as a component of, a specified entity or substance.
-
D.
venomPotency
Indicates the degree of strength or toxicity of an entity’s venom in affecting another entity.
-
E.
hasAntivenom
Indicates that an entity possesses or provides an antivenom specifically effective against another entity’s venom.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 3:04 a.m.