Triple
T342667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Victoria |
E6869
|
entity |
| Predicate | invasiveSpecies |
P6138
|
FINISHED |
| Object | water hyacinth |
—
|
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: water hyacinth | Statement: [Lake Victoria, invasiveSpecies, water hyacinth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invasiveSpecies Context triple: [Lake Victoria, invasiveSpecies, water hyacinth]
-
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.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
C.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
-
D.
involvesPlant
Indicates that the relationship or action includes or pertains to a plant as a participating entity.
-
E.
featuresSpecies
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eafef8c88190a5932eb2c6ac4a5d |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e9530c98819085025efe4e04aa7e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.