Triple
T13574442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsavo River |
E324245
|
entity |
| Predicate | majorWatercourseOf |
P57854
|
FINISHED |
| Object | southeastern Kenya |
—
|
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: southeastern Kenya | Statement: [Tsavo River, majorWatercourseOf, southeastern Kenya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorWatercourseOf Context triple: [Tsavo River, majorWatercourseOf, southeastern Kenya]
-
A.
isMajorWatercourseOf
chosen
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
-
B.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
C.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
-
D.
hasMajorRiverSystem
Indicates that an entity possesses or is traversed by a primary, large-scale river network that significantly characterizes its hydrology or geography.
-
E.
majorRiverSource
Indicates that one entity is the primary originating source or headwaters location of a major 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb02b1f108190a12af382d1de70bb |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.