Triple

T25970418
Position Surface form Disambiguated ID Type / Status
Subject Jakarta river system E645793 entity
Predicate instanceOf P0 FINISHED
Object urban river network C6053 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: urban river network
Context triple: [Jakarta river system, instanceOf, urban river network]
  • A. urban watercourse
    An urban watercourse is a natural or engineered channel of flowing water that runs through a city or town, shaped and managed by surrounding urban infrastructure and land use.
  • B. waterway network chosen
    A waterway network is an interconnected system of natural and artificial water channels (such as rivers, canals, and streams) designed or utilized for the movement, distribution, and management of water and waterborne transport.
  • C. river corridor
    A river corridor is the linear landscape surrounding a river, including its channel, banks, floodplain, and adjacent habitats, through which water, sediment, organisms, and energy flow and interact.
  • D. river structure
    A river structure is any engineered or natural formation built in, on, or alongside a river to influence its flow, stability, navigation, or ecological function.
  • E. river basin
    A river basin is the land area drained by a river and all its tributaries, bounded by topographic divides that separate it from adjacent basins.
  • F. None of above.

Provenance (1 batch)

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_69e77e8768648190b27bb578f14bcb88 completed April 21, 2026, 1:41 p.m.
Created at: April 22, 2026, 8:50 a.m.