Triple

T21953902
Position Surface form Disambiguated ID Type / Status
Subject Oscarsborg Fortress E542133 entity
Predicate locatedIn P40 FINISHED
Object Frogn 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: Frogn | Statement: [Oscarsborg Fortress, locatedIn, Frogn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frogn
Context triple: [Oscarsborg Fortress, locatedIn, Frogn]
  • A. Frogn chosen
    Frogn is a coastal municipality in Viken county, Norway, known for the historic Oscarsborg Fortress in the Oslofjord.
  • B. Fjugesta
    Fjugesta is a small locality in central Sweden that serves as the main town of Lekeberg Municipality in Örebro County.
  • C. Frosta
    Frosta is a rural municipality and peninsula in Trøndelag county, Norway, known for its fertile farmland and historical significance as a medieval assembly site.
  • D. Flen
    Flen is a small Swedish town known as the administrative center of Flen Municipality in the province of Södermanland.
  • E. Floen
    Floen is a small lake situated in Norway’s Oldedalen valley, known for its scenic glacial surroundings.
  • 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_69e0c47ef0e48190a50e1bcc43f4b3fd completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1243dfb4081909bc7a722843ffea7 completed April 28, 2026, 9:18 p.m.
Created at: April 16, 2026, 7:59 p.m.