Triple

T17138773
Position Surface form Disambiguated ID Type / Status
Subject Kampar River E415907 entity
Predicate hasTidalBore P57287 FINISHED
Object Bono wave 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: Bono wave | Statement: [Kampar River, hasTidalBore, Bono wave]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTidalBore
Context triple: [Kampar River, hasTidalBore, Bono wave]
  • A. hasMaximumTidalBoreHeight
    Indicates that one entity has a specified greatest recorded or expected height of its tidal bore.
  • B. hasTidalRange
    Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
  • C. containsTidalFeatures chosen
    Indicates that one entity exhibits observable tidal features caused by gravitational interactions with another entity.
  • D. hasTidalConnection
    Indicates that one entity is linked to another through the movement, influence, or exchange of tidal waters.
  • E. isTidal
    Indicates that something is influenced or driven by tidal forces or tidal movements.
  • 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_69d886d15af4819092f92f8a129763e6 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3f2d1277881909325ffd2a7aa4873 completed April 18, 2026, 9:08 p.m.
PD Predicate disambiguation batch_69e3830192ac819091344a9e5a36c8c9 completed April 18, 2026, 1:11 p.m.
Created at: April 10, 2026, 5:36 a.m.