Triple

T31279890
Position Surface form Disambiguated ID Type / Status
Subject 武庫川 E797632 entity
Predicate hasRiverbankUse P85477 FINISHED
Object parks 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: parks | Statement: [武庫川, hasRiverbankUse, parks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRiverbankUse
Context triple: [武庫川, hasRiverbankUse, parks]
  • A. hasRiverbanksUse chosen
    Indicates how the riverbanks of a river or watercourse are used or managed (e.g., for agriculture, recreation, conservation, or infrastructure).
  • B. hasRiverUse
    Indicates that one entity makes use of a river associated with another entity, such as for transport, irrigation, recreation, or other purposes.
  • C. hasWaterfrontUse
    Indicates that an entity is used, designated, or suitable for activities or purposes directly related to a waterfront or shoreline area.
  • D. hasParkAlongBank
    Indicates that a park is located adjacent to or running alongside the bank of a water body.
  • E. hasRiverBankSettlement
    Indicates that a settlement is located on or directly adjacent to the bank of a river.
  • 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_69f224def9088190a37034eab3daf57f completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f7886be6d8819095ec62e4f2cee858 completed May 3, 2026, 5:39 p.m.
PD Predicate disambiguation batch_69f7841440f48190b4346c08855951d2 completed May 3, 2026, 5:21 p.m.
Created at: April 29, 2026, 9:13 p.m.