Triple

T4961378
Position Surface form Disambiguated ID Type / Status
Subject Maasvlakte E111414 entity
Predicate namedAfter P63 FINISHED
Object river Meuse (Maas) E25802 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: river Meuse (Maas) | Statement: [Maasvlakte, namedAfter, river Meuse (Maas)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: river Meuse (Maas)
Context triple: [Maasvlakte, namedAfter, river Meuse (Maas)]
  • A. Meuse chosen
    The Meuse is a major European river flowing through France, Belgium, and the Netherlands, historically important for transport, trade, and the development of surrounding regions.
  • B. Meuse
    Meuse is a department in northeastern France known for its rural landscapes and significant World War I battlefields, including Verdun.
  • C. Rijn
    Rijn is the Dutch name for the major European river known in English as the Rhine.
  • D. 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.
  • E. 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.
  • 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_69bd4419393c819086319a6fe4bf8542 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd71dc06a48190827d54a5c0351aab completed March 20, 2026, 4:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69bef7e68058819089e179a29ab700bc completed March 21, 2026, 7:56 p.m.
Created at: March 20, 2026, 1:32 p.m.