Triple

T7075217
Position Surface form Disambiguated ID Type / Status
Subject St. Hanshaugen E164799 entity
Predicate contains P35 FINISHED
Object Lovisenberg E551708 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: Lovisenberg | Statement: [St. Hanshaugen, contains, Lovisenberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lovisenberg
Context triple: [St. Hanshaugen, contains, Lovisenberg]
  • A. Lovisenberg chosen
    Lovisenberg is a residential neighborhood in Oslo, Norway, known for its central location and the presence of Lovisenberg Diaconal Hospital and related educational institutions.
  • B. Hohberg
    Hohberg is a municipality in the Ortenau district of Baden-Württemberg in southwestern Germany.
  • C. Luxenberg
    Luxenberg is an alternative spelling or variant form of the name "Luxemburg," which can refer to the European country Luxembourg or the surname of notable individuals such as revolutionary Rosa Luxemburg.
  • D. Hintonburg
    Hintonburg is a historic, arts-oriented urban neighbourhood in west-central Ottawa, known for its mix of residential streets, independent shops, and cultural venues.
  • E. Löwenberg
    Löwenberg is a town in Germany known for its cultural and municipal partnership as a twin town of Weilburg.
  • 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_69c6887cbc6c8190bdfac42d940f4d8a completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e4ce3d3c81908cbb912b256aadbf completed March 27, 2026, 8:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69c79468c7688190bf10433f05e77574 completed March 28, 2026, 8:42 a.m.
Created at: March 27, 2026, 2:40 p.m.