Triple
T28645960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haya |
E725055
|
entity |
| Predicate | usesLakeResources |
P28866
|
FINISHED |
| Object | fishing on Lake Victoria |
—
|
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: fishing on Lake Victoria | Statement: [Haya, usesLakeResources, fishing on Lake Victoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLakeResources Context triple: [Haya, usesLakeResources, fishing on Lake Victoria]
-
A.
usesLakeFor
chosen
Indicates that an entity utilizes a lake as a resource or setting for some purpose, activity, or function.
-
B.
hasLakes
Indicates that one entity possesses, contains, or is characterized by the presence of one or more lakes.
-
C.
hasManyLakes
Indicates that an entity possesses or is associated with a large number of lakes.
-
D.
hasLakeLandscape
Indicates that an entity features or is characterized by a landscape that includes a lake.
-
E.
hasLakeThatRepresents
Indicates a relationship where a lake serves as a symbolic or representative feature for something, such as a place, concept, or 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 4:48 a.m.