Triple
T15461529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardanger Bridge |
E371911
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Eidfjord |
—
|
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: Eidfjord | Statement: [Hardanger Bridge, locatedNear, Eidfjord]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eidfjord Context triple: [Hardanger Bridge, locatedNear, Eidfjord]
-
A.
Eidfjord
chosen
Eidfjord is a small Norwegian village and municipality in Vestland county, known for its dramatic fjord landscape, waterfalls, and status as a popular cruise and tourist destination.
-
B.
Sunnfjord
Sunnfjord is a district in Vestland county in Western Norway, known for its fjords, valleys, and traditional rural communities.
-
C.
Sifjord
Sifjord is a small coastal village in northern Norway, situated on the island of Senja within Troms og Finnmark county.
-
D.
Osafjorden
Osafjorden is a side fjord of Norway’s Hardangerfjord, known for its steep mountain scenery and tranquil, narrow waters.
-
E.
Fanefjord
Fanefjord is a small village on the Danish island of Møn, known for its historic countryside setting and proximity to the medieval Fanefjord Church.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f17663c8190b995c7c3129c90d6 |
completed | April 16, 2026, 1:44 a.m. |
Created at: April 10, 2026, 3:32 a.m.