Triple
T3504139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somme |
E74035
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Aisne |
E83838
|
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: Aisne | Statement: [Somme, borderedBy, Aisne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aisne Context triple: [Somme, borderedBy, Aisne]
-
A.
Aisne
chosen
Aisne is a department in northern France known for its historic towns, World War I battlefields, and rural landscapes.
-
B.
Aisne
Aisne is a river in northeastern France that flows through the Champagne and Picardy regions before joining the Oise River.
-
C.
Marne
The Marne is a major river in northeastern France that flows through the Île-de-France region before joining the Seine near Paris.
-
D.
Oise-Aisne
Oise-Aisne is a region in northern France that was a major World War I battlefield, notably during the Aisne and Oise-Aisne offensives.
-
E.
Nièvre
Nièvre is a rural department in central France’s Bourgogne-Franche-Comté region, known for its rolling countryside, the Loire River, and its capital city Nevers.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf22b1c8190956141d8fb924210 |
completed | March 8, 2026, 6:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdacbe49ac81908f014539a1147a4f |
completed | March 20, 2026, 8:23 p.m. |
Created at: March 8, 2026, 3:18 p.m.