Triple

T16428579
Position Surface form Disambiguated ID Type / Status
Subject Vestnertor Tower E399010 entity
Predicate locatedNear P294 FINISHED
Object Vestnertor gate E567379 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: Vestnertor gate | Statement: [Vestnertor Tower, locatedNear, Vestnertor gate]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vestnertor gate
Context triple: [Vestnertor Tower, locatedNear, Vestnertor gate]
  • A. Nordre gate
    Nordre gate is a central pedestrian shopping street in Trondheim, Norway, known for its stores, cafés, and vibrant urban life.
  • B. Møllergata
    Møllergata is a central street in Oslo, Norway, known for its historic buildings and proximity to key political and commercial areas.
  • C. Toftes gate
    Toftes gate is a notable street in the Grünerløkka district of Oslo, Norway, known for its mix of historic buildings, cafes, and urban neighborhood life.
  • D. Hedmarksgata
    Hedmarksgata is a street located in the Vålerenga neighborhood of Oslo, Norway.
  • E. Søndre gate chosen
    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.
  • 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_69d87f2b9024819085c20e52de95d583 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e328fc223c8190bbed29907351a6f6 completed April 18, 2026, 6:47 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00458331748190a4bd1c5d2d466e6d completed May 10, 2026, 8:44 a.m.
Created at: April 10, 2026, 5:09 a.m.