Triple
T9673167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulverston |
E234079
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Albert, Somme |
E391539
|
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: Albert, Somme | Statement: [Ulverston, hasTwinTown, Albert, Somme]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Albert, Somme Context triple: [Ulverston, hasTwinTown, Albert, Somme]
-
A.
Albert, Somme
chosen
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.
-
B.
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.
-
C.
Aisne
Aisne is a department in northern France known for its historic towns, World War I battlefields, and rural landscapes.
-
D.
Aisne
Aisne is a river in northeastern France that flows through the Champagne and Picardy regions before joining the Oise River.
-
E.
Oise
Oise is a major river in northern France that flows through regions such as Picardy and Île-de-France before joining the Seine near Paris.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6c05c481909885bfdb850e7527 |
completed | April 1, 2026, 10:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d18a2d030c8190ada52e855bc9afc8 |
completed | April 4, 2026, 10:01 p.m. |
Created at: March 30, 2026, 8:15 p.m.