Triple
T17031596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linepithema |
E413210
|
entity |
| Predicate | containsInvasiveSpecies |
P6138
|
FINISHED |
| Object | Linepithema humile |
—
|
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: Linepithema humile | Statement: [Linepithema, containsInvasiveSpecies, Linepithema humile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsInvasiveSpecies Context triple: [Linepithema, containsInvasiveSpecies, Linepithema humile]
-
A.
hasInvasiveSpecies
chosen
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.
isInvasive
Indicates that one entity intrudes upon, spreads into, or encroaches on another entity or environment in a disruptive or unwanted manner.
-
C.
containsWildSpecies
Indicates that one entity includes, houses, or encompasses wild (non-domesticated) species within its scope or boundaries.
-
D.
hasWeedySpecies
Indicates that an entity is associated with plant species considered weedy, invasive, or prone to unwanted spread.
-
E.
containsVenomousSpecies
Indicates that the referenced entity includes within it one or more species that are venomous.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d9e7d481909d3d5bd241bd68f1 |
completed | April 18, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.