Triple
T4036438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aisne |
E83838
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Somme |
E74035
|
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, borders, Somme]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Somme Context triple: [Aisne, borders, Somme]
-
A.
Somme River
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 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.
-
E.
Somme, France
chosen
Somme, France is a department in northern France best known as the site of major World War I battles, including the Battle of the Somme.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb349e648190b9f227df4cd76fa0 |
completed | March 9, 2026, 4:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b556415ebc8190a528c7e22dbf70df |
completed | March 14, 2026, 12:36 p.m. |
Created at: March 9, 2026, 3:36 p.m.