Triple
T3517918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardangerfjord |
E74351
|
entity |
| Predicate | hasBranch |
P35
|
FINISHED |
| Object | Sørfjorden |
E378636
|
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: Sørfjorden | Statement: [Hardangerfjord, hasBranch, Sørfjorden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sørfjorden Context triple: [Hardangerfjord, hasBranch, Sørfjorden]
-
A.
Bremnesfjorden
Bremnesfjorden is a fjord in Norway known for its coastal landscape along the island of Averøya.
-
B.
Tyrifjorden
Tyrifjorden is one of Norway’s largest lakes, known for its scenic surroundings and importance as a recreational and ecological area in Eastern Norway.
-
C.
Beisfjorden
Beisfjorden is a fjord in Nordland county, Norway, known as an inner branch of the larger Ofotfjord near the town of Narvik.
-
D.
Randsfjorden
Randsfjorden is one of Norway’s largest inland lakes, located in Eastern Norway and known for its elongated shape and surrounding forested landscapes.
-
E.
Eidfjorden
chosen
Eidfjorden is a scenic inner branch of Norway’s Hardangerfjord, known for its steep mountainsides, waterfalls, and fjord landscapes.
- 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc32f90081908960acb3e94402be |
completed | March 8, 2026, 6:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4c3718bd88190bec2f4cfda0010ae |
completed | March 14, 2026, 2:09 a.m. |
Created at: March 8, 2026, 3:19 p.m.