Triple

T9291235
Position Surface form Disambiguated ID Type / Status
Subject Aisne E223521 entity
Predicate borderedBy P224 FINISHED
Object Somme E83858 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: Somme | Statement: [Aisne, borderedBy, Somme]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Somme
Context triple: [Aisne, borderedBy, Somme]
  • A. Somme River chosen
    The Somme River is a waterway in northern France that became historically significant as the site of one of World War I’s largest and bloodiest battles.
  • B. Verdun
    Verdun is a borough of Montreal, Quebec, known for its historic waterfront along the St. Lawrence River and its mix of residential neighborhoods and urban amenities.
  • C. Yser Front
    The Yser Front was a key World War I defensive line in western Belgium where Belgian forces halted the German advance along the Yser River.
  • D. Battle of the Sambre
    The Battle of the Sambre was a major engagement in 57 BC during Julius Caesar’s Gallic Wars, in which Roman forces defeated the Nervii and their allies in northern Gaul.
  • E. Battle of Verdun
    The Battle of Verdun was one of the longest and bloodiest engagements of World War I, symbolizing the brutal attrition warfare on the Western Front between France and Germany in 1916.
  • 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_69ca8422ddf881908a3f8f876c9f53aa completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd0865a7108190b807afd259980db2 completed April 1, 2026, 11:58 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0e3865ef081909f5f258cac44ae8b completed April 4, 2026, 10:10 a.m.
Created at: March 30, 2026, 7:35 p.m.