Triple
T21150956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deux-Sèvres |
E521185
|
entity |
| Predicate | hasBorderWith |
P224
|
FINISHED |
| Object | Vienne |
—
|
NE NERFINISHED |
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: Vienne | Statement: [Deux-Sèvres, hasBorderWith, Vienne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vienne Context triple: [Deux-Sèvres, hasBorderWith, Vienne]
-
A.
Vienne
chosen
Vienne is a major river in west-central France that flows through the Limousin region before joining the Loire.
-
B.
Vienne
Vienne is a historic town in southeastern France known for its well-preserved Roman and medieval heritage, including ancient temples, a Roman theater, and a Gothic cathedral.
-
C.
Vienna
Vienna is the capital city of Austria, renowned for its rich imperial history, classical music heritage, and vibrant cultural and intellectual life.
-
D.
Vienna
Vienna is a small town in Dane County, Wisconsin, known for its rural character and proximity to the Madison metropolitan area.
-
E.
Vienna
Vienna is the ancient Roman name for the city of Vienne in southeastern France, which was an important Roman settlement and administrative center in Gaul.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72401830c8190a2008c40c4174d97 |
completed | April 21, 2026, 7:15 a.m. |
Created at: April 16, 2026, 2:58 p.m.