Triple
T3517937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardangerfjord |
E74351
|
entity |
| Predicate | hasSettlementOnShore |
P16159
|
FINISHED |
| Object | Ulvik |
E366898
|
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: Ulvik | Statement: [Hardangerfjord, hasSettlementOnShore, Ulvik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ulvik Context triple: [Hardangerfjord, hasSettlementOnShore, Ulvik]
-
A.
Ulvik
chosen
Ulvik is a small scenic municipality and village area in Vestland county, Norway, known for its fjord landscape, fruit orchards, and location along the inner reaches of the Hardanger region.
-
B.
Iveland
Iveland is a small rural municipality in southern Norway known for its forests, agriculture, and mineral resources.
-
C.
Ulsta
Ulsta is a small settlement on the island of Yell in Shetland, Scotland, known primarily for its ferry terminal linking Yell to the Shetland mainland.
-
D.
Thamerdal
Thamerdal is a residential neighborhood within the Dutch town of Uithoorn in the province of North Holland.
-
E.
Blakstad
Blakstad is a village in Agder county, Norway, known as the main local hub for services and administration in the surrounding Froland area.
- 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_69b3bb809d288190b4904b292fe9a627 |
completed | March 13, 2026, 7:23 a.m. |
Created at: March 8, 2026, 3:19 p.m.