Triple
T6266766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lom, Norway |
E140432
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Lesja |
E433526
|
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: Lesja | Statement: [Lom, Norway, borders, Lesja]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lesja Context triple: [Lom, Norway, borders, Lesja]
-
A.
Lesja
chosen
Lesja is a rural municipality in Innlandet county, Norway, known for its mountainous landscapes, agriculture, and outdoor recreation opportunities.
-
B.
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.
-
C.
Jogne
Jogne is a river in western Switzerland that flows through the canton of Fribourg before joining the Sarine.
-
D.
Eidskog
Eidskog is a rural municipality in Innlandet county, Norway, known for its forests, lakes, and location along the Swedish border.
-
E.
Eljas
Eljas is a municipality in western Spain’s Extremadura region, known for its distinctive local Fala language and cultural identity.
- 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_69c008cabc4081909723e2547c9d6cc0 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0639fdad081908492c44d369df8c5 |
completed | March 22, 2026, 9:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c51939cc6081909e491bd16fab595b |
completed | March 26, 2026, 11:32 a.m. |
Created at: March 22, 2026, 4:25 p.m.