Triple
T21963581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hedmarksgata |
E542399
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Hedmarksgata (Norwegian) |
—
|
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: Hedmarksgata (Norwegian) | Statement: [Hedmarksgata, hasNameInLanguage, Hedmarksgata (Norwegian)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hedmarksgata (Norwegian) Context triple: [Hedmarksgata, hasNameInLanguage, Hedmarksgata (Norwegian)]
-
A.
Hedmarksgata
chosen
Hedmarksgata is a street located in the Vålerenga neighborhood of Oslo, Norway.
-
B.
Nordre gate
Nordre gate is a central pedestrian shopping street in Trondheim, Norway, known for its stores, cafés, and vibrant urban life.
-
C.
Møllergata
Møllergata is a central street in Oslo, Norway, known for its historic buildings and proximity to key political and commercial areas.
-
D.
Søndre gate
Søndre gate is a central street in Trondheim, Norway, known for its shops, cafes, and role as a main thoroughfare in the Midtbyen district.
-
E.
Nedre Slottsgate
Nedre Slottsgate is a central street in downtown Oslo, Norway, known for its shops, cafes, and proximity to major squares and landmarks.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12458e4488190a04f8d3958854b49 |
completed | April 28, 2026, 9:19 p.m. |
Created at: April 16, 2026, 8:01 p.m.