Triple
T7712671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amiens |
E174798
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Somme River |
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 River | Statement: [Amiens, locatedOn, Somme River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Somme River Context triple: [Amiens, locatedOn, Somme River]
-
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.
Marne
The Marne is a major river in northeastern France that flows through the Île-de-France region before joining the Seine near Paris.
-
C.
Marne
Marne is a small city located in Cass County in the southwestern part of the U.S. state of Iowa.
-
D.
Albert, Somme
Albert, Somme is a small town in northern France that served as a key logistical and front-line center during the Battle of the Somme in World War I.
-
E.
Oise River
The Oise River is a major waterway in northern France and southern Belgium that flows into the Seine and serves as an important route for inland navigation and commerce.
- 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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702c96e388190898165f84d646c0e |
completed | March 27, 2026, 10:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8acd3e9f88190adf42ab42c21b722 |
completed | March 29, 2026, 4:38 a.m. |
Created at: March 27, 2026, 4:04 p.m.