Triple

T14056160
Position Surface form Disambiguated ID Type / Status
Subject Amaliegade E338223 entity
Predicate hasNotableBuilding P1544 FINISHED
Object Amaliegade 79 E338223 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: Amaliegade 79 | Statement: [Amaliegade, hasNotableBuilding, Amaliegade 79]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amaliegade 79
Context triple: [Amaliegade, hasNotableBuilding, Amaliegade 79]
  • A. Amaliegade chosen
    Amaliegade is a historic street in central Copenhagen, Denmark, known for its elegant 18th-century townhouses and proximity to the royal Amalienborg Palace.
  • B. Pilestredet
    Pilestredet is a central street in Oslo, Norway, known for hosting parts of Oslo Metropolitan University's main campus and various urban institutions.
  • C. Humlegården
    Humlegården is a large historic park in central Stockholm known for its green spaces, walking paths, and recreational areas.
  • D. Gavlerinken
    Gavlerinken is the former name of Monitor ERP Arena, an indoor ice hockey and events venue in Gävle, Sweden.
  • E. Langebrug
    Langebrug is a historic bridge spanning the Spaarne River in the Dutch city of Haarlem.
  • 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_69d81c67ba6c819091935650dfb3b895 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de3c8d1aa48190a5055d15d9fa220c completed April 14, 2026, 1:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd3d027450819098f4f9be71451ec5 completed May 8, 2026, 1:31 a.m.
Created at: April 9, 2026, 10:20 p.m.