Triple

T2415340
Position Surface form Disambiguated ID Type / Status
Subject Amundsen–Ellsworth–Nobile expedition E52288 entity
Predicate routePoint P36479 FINISHED
Object Oslo E3654 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: Oslo | Statement: [Amundsen–Ellsworth–Nobile expedition, routePoint, Oslo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oslo
Context triple: [Amundsen–Ellsworth–Nobile expedition, routePoint, Oslo]
  • A. Oslo chosen
    Oslo is the capital and largest city of Norway, known as a major cultural, economic, and governmental center.
  • B. Trondheim
    Trondheim is a historic Norwegian city in Trøndelag county, known for its medieval Nidaros Cathedral and role as a former capital of Norway.
  • C. Bergen
    Bergen is Norway's second-largest city, renowned for its historic harbor, surrounding mountains and fjords, and role as a former Hanseatic trading hub.
  • D. Stavanger
    Stavanger is a coastal city in southwestern Norway known for its oil industry hub status, historic wooden houses, and proximity to natural attractions like the Lysefjord and Preikestolen.
  • E. Tromsø
    Tromsø is a city in northern Norway known for its Arctic location, vibrant cultural scene, and prominence as a viewing spot for the Northern Lights.
  • 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_69ab495622948190bc6bc6e4cddaf645 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abd0d942048190bc5c715faa850632 completed March 7, 2026, 7:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69aebef5ac7c81908015969c04fcc425 completed March 9, 2026, 12:37 p.m.
Created at: March 6, 2026, 9:41 p.m.