Triple
T15323829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kampong Ayer |
E366358
|
entity |
| Predicate | hasWaterSupply |
P105704
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kampong Ayer, hasWaterSupply, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterSupply Context triple: [Kampong Ayer, hasWaterSupply, yes]
-
A.
hasDrinkingWaterFacilities
chosen
Indicates that a place or facility provides access to safe drinking water sources or infrastructure for people to use.
-
B.
sourceOfWaterSupply
Indicates that one entity serves as the origin or provider of another entity’s water supply.
-
C.
hasWaterUse
Indicates a relationship where one entity utilizes or consumes water for a particular purpose, process, or function.
-
D.
hasWaterResourceType
Indicates that an entity is associated with a specific type or category of water resource.
-
E.
hasWaterResourceRole
Indicates that an entity participates in a water-related resource context with a specified functional role (e.g., source, user, manager, or regulator of water resources).
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd5ce0c819093c9a14de549dff6 |
completed | April 16, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.