Triple

T14626349
Position Surface form Disambiguated ID Type / Status
Subject Beauvais E343358 entity
Predicate locatedOn P40 FINISHED
Object Thérain River E1044316 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: Thérain River | Statement: [Beauvais, locatedOn, Thérain River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thérain River
Context triple: [Beauvais, locatedOn, Thérain River]
  • A. Thérain River chosen
    The Thérain River is a watercourse in northern France that flows through the Picardy region before joining the Oise River.
  • B. Vistre River
    The Vistre River is a small watercourse in southern France that flows through the city of Nîmes before reaching the Mediterranean region.
  • C. Nive River
    The Nive River is a waterway in southwestern France that flows through the Basque Country and joins the Adour River at Bayonne before reaching the Atlantic coast.
  • D. Calavon River
    The Calavon River is a watercourse in southeastern France that flows through the Luberon region of Provence before joining the Durance River.
  • E. Ource River
    The Ource River is a small river in northeastern France that flows through the Champagne region, including the village of Essoyes, before joining the Seine.
  • 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_69d822dffc3c8190aa173b90761bffda completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb46a4a9081908472b0a542028a7f completed April 14, 2026, 9:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69feb7cfd9d08190b5b95f6dc0a08537 completed May 9, 2026, 4:28 a.m.
Created at: April 10, 2026, 1:26 a.m.