Triple
T36464251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lactoria cornuta |
E898380
|
entity |
| Predicate | defenseEffect |
P6933
|
FINISHED |
| Object | toxin released into surrounding water |
—
|
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: toxin released into surrounding water | Statement: [Lactoria cornuta, defenseEffect, toxin released into surrounding water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenseEffect Context triple: [Lactoria cornuta, defenseEffect, toxin released into surrounding water]
-
A.
defenseFunction
Indicates that an entity serves a protective or defensive role against threats, attacks, or harm to another entity or system.
-
B.
defenseResult
chosen
Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
-
C.
defenseFrequency
Indicates how often a defensive action or protective behavior occurs within a given context or time frame.
-
D.
defenseTrigger
Indicates that one entity initiates or activates a defensive response or mechanism in another entity.
-
E.
defenseStatus
Indicates the current state or condition of an entity’s defensive posture or protective readiness in a given context.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.