Triple

T22877974
Position Surface form Disambiguated ID Type / Status
Subject Stiftsgården E567377 entity
Predicate locatedOn P40 FINISHED
Object Munkegata 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: Munkegata | Statement: [Stiftsgården, locatedOn, Munkegata]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Munkegata
Context triple: [Stiftsgården, locatedOn, Munkegata]
  • A. Munkegata chosen
    Munkegata is a central street in Trondheim, Norway, known for its shops, services, and role as a key thoroughfare in the Midtbyen city center.
  • B. Sannergata
    Sannergata is a street in the Grünerløkka district of Oslo, Norway, known for its urban character and proximity to cafés, shops, and residential areas.
  • C. Krokstadøra
    Krokstadøra is a small village in Trøndelag county, Norway, situated along the Orkla River and serving as a local community center within the municipality.
  • D. Namegata
    Namegata is a city in Ibaraki Prefecture, Japan, known for its agricultural production and location along Lake Kasumigaura.
  • E. Dokkveien
    Dokkveien is a street located in the Vika neighborhood of central Oslo, Norway, near the city’s waterfront and business district.
  • 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_69e24589d8348190b96422d13a678bc1 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17f5966c08190a9ded9b19b166112 completed April 29, 2026, 3:47 a.m.
Created at: April 17, 2026, 3:39 p.m.