Triple
T21307575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lausanne–Brig railway line |
E525239
|
entity |
| Predicate | endPoint |
P390
|
FINISHED |
| Object | Brig |
E145812
|
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: Brig | Statement: [Lausanne–Brig railway line, endPoint, Brig]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brig Context triple: [Lausanne–Brig railway line, endPoint, Brig]
-
A.
Brig
chosen
Brig is a historic Swiss town in the canton of Valais, known as a regional transport hub and gateway to the surrounding Alpine passes.
-
B.
Brigend
Brigend is a territorial designation in Scotland associated with the title of Montgomery of Brigend.
-
C.
BRIGG
BRIGG is a small market town and civil parish in North Lincolnshire, England, known historically for its agricultural trade and traditional markets.
-
D.
Guncati
Guncati is a village located within the municipality of Barajevo in the city of Belgrade, Serbia.
-
E.
Capitão-de-fragata
Capitão-de-fragata is a mid-senior naval officer rank, typically equivalent to a commander in many navies.
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75aa7b2f08190bea46f0107bcc045 |
completed | April 21, 2026, 11:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a099ed5c7008190aa5696191389ed59 |
completed | May 17, 2026, 10:56 a.m. |
Created at: April 16, 2026, 4:05 p.m.