Triple

T3869360
Position Surface form Disambiguated ID Type / Status
Subject European inland shipping network E91944 entity
Predicate hasComponent P35 FINISHED
Object Scheldt River E12931 NE 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: Scheldt River | Statement: [European inland shipping network, hasComponent, Scheldt River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Scheldt River
Context triple: [European inland shipping network, hasComponent, Scheldt River]
  • A. Scheldt chosen
    The Scheldt is a major river in Western Europe that flows through France, Belgium, and the Netherlands, playing a key role in regional trade and navigation.
  • B. Eems
    Eems is the Dutch name for the Ems River, a major waterway in northwestern Europe that flows through Germany and the Netherlands into the North Sea.
  • C. Kanaal Brussel-Schelde
    Kanaal Brussel-Schelde is a major Belgian waterway linking Brussels with the Scheldt River, serving both commercial shipping and recreational activities.
  • D. Rijn
    Rijn is the Dutch name for the major European river known in English as the Rhine.
  • E. Nederrijn
    The Nederrijn is a major distributary branch of the Rhine River in the Netherlands, flowing through cities such as Arnhem and forming an important part of the Dutch river system.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69aed9645f348190a9868e7cef56ab7e completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeec533828819080f52dae15fdbecd completed March 9, 2026, 3:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69b52840f9b4819098fa220189222210 completed March 14, 2026, 9:20 a.m.
Created at: March 9, 2026, 3:20 p.m.