Triple
T37616804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basoga |
E935945
|
entity |
| Predicate | regionMainLake |
P1025
|
FINISHED |
| Object | Lake Victoria |
—
|
NE NERFINISHED |
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: Lake Victoria | Statement: [Basoga, regionMainLake, Lake Victoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionMainLake Context triple: [Basoga, regionMainLake, Lake Victoria]
-
A.
mouthLake
Indicates the location where a river or stream flows into and forms part of a lake.
-
B.
lakeIs
Indicates that one entity is classified as or functions as a lake in relation to another entity or context.
-
C.
lakeIsOneOf
Indicates that the subject lake belongs to a specified set or category of lakes.
-
D.
majorTerminalLake
Indicates that a body of water is a significant terminal lake, meaning it has no natural outflow and water leaves primarily through evaporation or seepage.
-
E.
hasMajorLake
chosen
Indicates that a geographic region or area contains at least one significant lake within its boundaries.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
Created at: May 3, 2026, 4:18 p.m.