Triple
T14028532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadeland |
E337526
|
entity |
| Predicate | hasMunicipality |
P847
|
FINISHED |
| Object | Lunner |
E433535
|
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: Lunner | Statement: [Hadeland, hasMunicipality, Lunner]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lunner Context triple: [Hadeland, hasMunicipality, Lunner]
-
A.
Lunner
chosen
Lunner is a rural municipality in Innlandet county, Norway, known for its forests, lakes, and role as part of the Hadeland traditional district.
-
B.
Lundell
Lundell is a Swedish surname most prominently associated with Ulf Lundell, a well-known rock musician, songwriter, and author.
-
C.
Lennertz
Lennertz is a German-origin surname borne by various individuals, including American composer Christopher Lennertz.
-
D.
Loerzer
Loerzer is the surname of Bruno Loerzer, a notable German First World War flying ace and later Luftwaffe general.
-
E.
Linderud
Linderud is a residential neighborhood in Oslo, Norway, known for its apartment blocks, shopping center, and access to public transportation.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fa830ac81908cb7df7c9e81e42a |
completed | April 14, 2026, 12:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbc335a474819084c310b10e0ded9a |
completed | May 6, 2026, 10:39 p.m. |
Created at: April 9, 2026, 10:20 p.m.