Triple

T17238870
Position Surface form Disambiguated ID Type / Status
Subject French Hainaut E418434 entity
Predicate river P165 FINISHED
Object Escaut NE NERFINISHED

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: Escaut | Statement: [French Hainaut, river, Escaut]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Escaut
Context triple: [French Hainaut, river, Escaut]
  • 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. Oldetrijne
    Oldetrijne is a small village in the municipality of Weststellingwerf in the Dutch province of Friesland.
  • C. Vaartsche Rijn
    Vaartsche Rijn is a historic canal in the Dutch province of Utrecht that connects the city of Utrecht with the Lower Rhine and forms part of its inland waterway network.
  • D. Dieuze
    Dieuze is a small commune in northeastern France, located in the Moselle department in the historical region of Lorraine.
  • E. Oude Maas
    The Oude Maas is a major distributary river in the western Netherlands that forms part of the complex Rhine–Meuse–Scheldt delta system.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d886d8e96081909870bff6c3d0bf09 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42dfdc8688190aceb223c19a48781 completed April 19, 2026, 1:21 a.m.
Created at: April 10, 2026, 5:39 a.m.