Triple
T16680316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Nakuru |
E405320
|
entity |
| Predicate | dominantAlgae |
P38050
|
FINISHED |
| Object | cyanobacteria |
—
|
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: cyanobacteria | Statement: [Lake Nakuru, dominantAlgae, cyanobacteria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantAlgae Context triple: [Lake Nakuru, dominantAlgae, cyanobacteria]
-
A.
dominantCommunity
Indicates that one community holds a prevailing or controlling influence, status, or presence over others within a given context.
-
B.
hasDominantSpecies
chosen
Indicates that one entity possesses or is characterized by a species that is predominant or most influential within it.
-
C.
dominantLifeformType
Indicates which type of lifeform holds primary dominance or control within a given context or environment.
-
D.
dominantEnvironment
Indicates the primary or prevailing environment or setting in which an entity most characteristically exists, operates, or exerts influence.
-
E.
dominantPlantFamily
Indicates that one plant family is the most prevalent or ecologically dominant group within a specified area, community, or 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37d6e74ec81909ea95c3e4b0113ab |
completed | April 18, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.