Triple
T19974258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stor-Elvdal |
E493646
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Ringsaker |
—
|
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: Ringsaker | Statement: [Stor-Elvdal, borders, Ringsaker]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ringsaker Context triple: [Stor-Elvdal, borders, Ringsaker]
-
A.
Ringsaker
chosen
Ringsaker is a municipality in Innlandet county, Norway, known for its agricultural landscapes along Lake Mjøsa and its proximity to the town of Hamar.
-
B.
Retinger
Retinger is the surname of Józef Retinger, a Polish political adviser and key organizer of early European integration efforts.
-
C.
Ring
Ring is a smart home security and video doorbell company known for its connected cameras and home monitoring services.
-
D.
Ring
Ring is a coastal Gaeltacht village in County Waterford, Ireland, known for its strong Irish-language community and cultural traditions.
-
E.
Ring
Ring is a Clojure web applications library and standard interface that underpins much of the Clojure web ecosystem by defining a simple, functional abstraction for HTTP requests and responses.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65bcb72048190aedb4f085ace0493 |
completed | April 20, 2026, 5 p.m. |
Created at: April 11, 2026, 3:23 p.m.