Triple
T14501477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gausdal |
E359649
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Segalstad bru |
E1088192
|
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: Segalstad bru | Statement: [Gausdal, hasSettlement, Segalstad bru]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Segalstad bru Context triple: [Gausdal, hasSettlement, Segalstad bru]
-
A.
Segalstad bru
chosen
Segalstad bru is a village in Innlandet county, Norway, known as the main local hub of Gausdal municipality.
-
B.
Beisfjord Bridge
Beisfjord Bridge is a road bridge in Narvik, Norway, that spans the Beisfjorden and forms part of the key transport route in the region.
-
C.
Sundklakkstraumen Bridge
Sundklakkstraumen Bridge is a road bridge in the Lofoten archipelago of Norway that connects the island of Gimsøya to neighboring land across the Sundklakkstraumen strait.
-
D.
Bryghusbroen
Bryghusbroen is a modern pedestrian and bicycle bridge in central Copenhagen that connects the Slotsholmen area with the waterfront and adjacent neighborhoods.
-
E.
Mjøsa Bridge
Mjøsa Bridge is a major road bridge in Innlandet county, Norway, spanning Lake Mjøsa and serving as a key transport link in the region.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de94dfe484819086dd971606e6478e |
completed | April 14, 2026, 7:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd7a420040819097ee73390d625338 |
completed | May 8, 2026, 5:53 a.m. |
Created at: April 10, 2026, 1:21 a.m.