Triple

T6371315
Position Surface form Disambiguated ID Type / Status
Subject Lesser periwinkle E143349 entity
Predicate invasiveness P70244 FINISHED
Object can be invasive outside native range 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 be invasive outside native range | Statement: [Lesser periwinkle, invasiveness, can be invasive outside native range]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: invasiveness
Context triple: [Lesser periwinkle, invasiveness, can be invasive outside native range]
  • A. hasInvasiveSpecies
    Indicates that an area, ecosystem, or habitat contains one or more species that are non-native and causing or likely to cause ecological, economic, or environmental harm.
  • B. invade
    Indicates entering another entity’s territory or domain, typically by force or without permission, in order to take control or exert dominance.
  • C. inversions
    Indicates a relationship where the usual order, position, or hierarchy between elements is reversed or turned upside down.
  • D. arity
    Indicates the number of arguments or participants that a relation or function takes.
  • E. virulence
    Indicates the degree to which a pathogen or harmful agent is capable of causing damage, disease, or severe effects in its host.
  • 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_69c008d8c61081908bcaf61510d881ed completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c068289eac8190a17affed87340c1f completed March 22, 2026, 10:07 p.m.
PD Predicate disambiguation batch_69c060ee055081908c79a1d151bd74cd completed March 22, 2026, 9:36 p.m.
PDg Predicate description generation batch_69c0623d23448190a75cf5d802fc0a02 completed March 22, 2026, 9:42 p.m.
Created at: March 22, 2026, 4:33 p.m.