Triple

T10436706
Position Surface form Disambiguated ID Type / Status
Subject Battle of Liège E246060 entity
Predicate involved P1063 FINISHED
Object Meuse River 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: Meuse River | Statement: [Battle of Liège, involved, Meuse River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Meuse River
Context triple: [Battle of Liège, involved, Meuse River]
  • A. Meuse
    Meuse is a department in northeastern France known for its rural landscapes and significant World War I battlefields, including Verdun.
  • B. 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.
  • C. Sambre
    The Sambre is a major river in northern France and southern Belgium that flows through the Walloon region before joining the Meuse at Namur.
  • D. Moselle River
    The Moselle River is a major European waterway flowing through France, Luxembourg, and Germany, renowned for its scenic valleys and wine-producing regions.
  • E. river Maas
    The river Maas, also known as the Meuse, is a major European waterway flowing through France, Belgium, and the Netherlands before emptying into the North Sea.
  • 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_69d381bf3dc08190bf35a2643e4e8f22 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4ea853c308190be95ae8dffe67ac1 completed April 7, 2026, 11:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69d95e5197cc8190ad70c665ec2f8fa8 completed April 10, 2026, 8:32 p.m.
Created at: April 6, 2026, 12:14 p.m.