Triple
T36464250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lactoria cornuta |
E898380
|
entity |
| Predicate | defenseTrigger |
P188146
|
FINISHED |
| Object | stress |
—
|
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: stress | Statement: [Lactoria cornuta, defenseTrigger, stress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenseTrigger Context triple: [Lactoria cornuta, defenseTrigger, stress]
-
A.
defenseFunction
Indicates that an entity serves a protective or defensive role against threats, attacks, or harm to another entity or system.
-
B.
defenseResult
Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
-
C.
defenseStatus
Indicates the current state or condition of an entity’s defensive posture or protective readiness in a given context.
-
D.
defenseIncludes
Indicates that a defense strategy, plan, or system contains or incorporates a particular component, measure, or element as part of it.
-
E.
defense
Indicates an action or relationship in which an entity protects, guards, or resists against a threat, attack, or criticism from another entity.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:10 p.m.