Triple
T10176629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ouahigouya |
E235867
|
entity |
| Predicate | hasNearbyWaterBodyType |
P49291
|
FINISHED |
| Object | seasonal ponds |
—
|
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: seasonal ponds | Statement: [Ouahigouya, hasNearbyWaterBodyType, seasonal ponds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyWaterBodyType Context triple: [Ouahigouya, hasNearbyWaterBodyType, seasonal ponds]
-
A.
hasNearbyWater
chosen
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
B.
hasBodyOfWaterType
Indicates that a body of water is classified as being of a particular type or category (such as lake, river, ocean, etc.).
-
C.
hasAssociatedWaterBody
Indicates that one entity is linked to, or occurs in connection with, a specific body of water such as a river, lake, or sea.
-
D.
hasWaterBodyCharacteristic
Indicates that a water body possesses a specified physical, chemical, or ecological characteristic.
-
E.
hasNearbyWaterInfrastructure
Indicates that a location or entity is situated close to water-related infrastructure such as pipes, treatment facilities, or distribution systems.
- 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_69ca84d1d5f88190ab878a1021ecff68 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdecd3a2688190bce277bffffcbf8b |
completed | April 2, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:11 p.m.