Triple

T23543884
Position Surface form Disambiguated ID Type / Status
Subject Sollerud E577833 entity
Predicate locatedIn P40 FINISHED
Object Ullern 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: Ullern | Statement: [Sollerud, locatedIn, Ullern]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ullern
Context triple: [Sollerud, locatedIn, Ullern]
  • A. Ullern chosen
    Ullern is a primarily residential borough in western Oslo, Norway, known for its affluent neighborhoods, green spaces, and proximity to the city center.
  • B. Vennesla
    Vennesla is a municipality in Agder county in southern Norway, known for its industrial heritage and scenic river valley setting.
  • C. Ullernåsen
    Ullernåsen is a residential hillside neighborhood in Oslo, Norway, known for its apartment blocks, green surroundings, and views over the western parts of the city.
  • D. Stryn
    Stryn is a municipality in Vestland county, Norway, known for its dramatic fjord and mountain landscapes, glaciers, and popular outdoor tourism activities.
  • E. Lærdal
    Lærdal is a municipality in Vestland county, Norway, known for its dramatic fjord landscapes, historic wooden architecture, and the UNESCO-listed Nærøyfjord area nearby.
  • 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_69e245f9d5d08190a4a20004e1784e20 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1ae1dbe188190bc4afe7bfa7cda0f completed April 29, 2026, 7:07 a.m.
Created at: April 17, 2026, 6:11 p.m.