Triple
T21308564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarangire River |
E525265
|
entity |
| Predicate | hasVegetationAlongBanks |
P113686
|
FINISHED |
| Object | acacia woodland |
—
|
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: acacia woodland | Statement: [Tarangire River, hasVegetationAlongBanks, acacia woodland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVegetationAlongBanks Context triple: [Tarangire River, hasVegetationAlongBanks, acacia woodland]
-
A.
hasRiparianZone
chosen
Indicates that an area is adjacent to and ecologically influenced by a body of water, forming its riparian (riverbank or shoreline) zone.
-
B.
hasAquaticPlantSpecies
Indicates that an entity contains, supports, or is associated with one or more species of aquatic plants.
-
C.
vegetationType
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
D.
vegetation
Indicates that an area or object is covered with, contains, or is characterized by plant life.
-
E.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75aa863688190a5e45248e31eec88 |
completed | April 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:06 p.m.