Triple
T3726744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Naivasha |
E81767
|
entity |
| Predicate | outflowType |
P8232
|
FINISHED |
| Object | subsurface seepage |
—
|
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: subsurface seepage | Statement: [Lake Naivasha, outflowType, subsurface seepage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outflowType Context triple: [Lake Naivasha, outflowType, subsurface seepage]
-
A.
outflow
Indicates the movement or discharge of something from an origin or source to the outside or to another location.
-
B.
flowType
chosen
Indicates the kind or category of flow (such as direction, pattern, or mode of movement/transfer) that characterizes the relationship between entities.
-
C.
flowsUnder
Indicates that one entity (typically a river, stream, or liquid) passes beneath another entity (such as a bridge, structure, or obstacle) along its course.
-
D.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
-
E.
regulatesOutflowOf
Indicates that one entity controls, modulates, or governs the rate or amount of outflow from another entity.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf7a6908190bd0c3bb5c55ab9ee |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.