Triple
T2394319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equatorial Lakes region |
E47612
|
entity |
| Predicate | hasLakeType |
P26466
|
FINISHED |
| Object | rift valley lakes |
—
|
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: rift valley lakes | Statement: [Equatorial Lakes region, hasLakeType, rift valley lakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLakeType Context triple: [Equatorial Lakes region, hasLakeType, rift valley lakes]
-
A.
hasMajorLake
Indicates that a geographic region or area contains at least one significant lake within its boundaries.
-
B.
hasNearbyLake
Indicates that one entity is located close to or in the vicinity of a lake.
-
C.
usesLakeFor
Indicates that an entity utilizes a lake as a resource or setting for some purpose, activity, or function.
-
D.
hasLagoon
Indicates that one entity possesses, contains, or is characterized by a lagoon in relation to another entity or location.
-
E.
hasHydrologicalType
chosen
Indicates a relationship where an entity is classified according to its hydrological category or type (e.g., river, lake, aquifer).
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc87827d88190bb2351a688e6de32 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.