Triple

T227363
Position Surface form Disambiguated ID Type / Status
Subject Congo River mouth E4339 entity
Predicate hasTides P1735 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: [Congo River mouth, hasTides, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTides
Context triple: [Congo River mouth, hasTides, yes]
  • A. hasTidalRange
    Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
  • B. isTidal chosen
    Indicates that something is influenced or driven by tidal forces or tidal movements.
  • C. hasNotableSea
    Indicates that an entity is associated with or contains a sea that is considered notable or significant.
  • D. hasOcean
    Indicates that a geographic region, country, or landmass is bordered by or directly adjacent to a particular ocean.
  • E. hasSeaIce
    Indicates that one entity possesses, contains, or is covered by sea ice in relation to another context or location.
  • 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_69a257363ffc81909757bde7ab3404da completed Feb. 28, 2026, 2:47 a.m.
NER Named-entity recognition batch_69a25d10ac248190a98dedabf5358668 completed Feb. 28, 2026, 3:12 a.m.
PD Predicate disambiguation batch_69a25b5877588190af694d060377f027 completed Feb. 28, 2026, 3:04 a.m.
Created at: Feb. 28, 2026, 2:53 a.m.