Triple

T20836820
Position Surface form Disambiguated ID Type / Status
Subject St. Olaf E512980 entity
Predicate deathPlace P21 FINISHED
Object Stiklestad, Norway 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: Stiklestad, Norway | Statement: [St. Olaf, deathPlace, Stiklestad, Norway]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stiklestad, Norway
Context triple: [St. Olaf, deathPlace, Stiklestad, Norway]
  • A. Stiklestad chosen
    Stiklestad is a historic village in Norway best known as the site of the Battle of Stiklestad in 1030, where King Olaf II (later Saint Olaf) was killed.
  • B. Orkanger
    Orkanger is a town in Trøndelag county, Norway, known as a regional commercial and service hub by the Orkdalsfjorden.
  • C. Folkestad, Norway
    Folkestad, Norway is a small village in Norway historically notable as the birthplace of King Haakon IV.
  • D. Avaldsnes
    Avaldsnes is a historic village in Rogaland county, Norway, known as one of the country’s oldest royal seats and a key center in Viking-era history.
  • E. Alstahaug
    Alstahaug is a coastal municipality in northern Norway known for its historic church, island landscapes, and maritime heritage.
  • 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_69e0b4cf62a88190bbf92351e9e57259 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c326daec8190bd4caa41a4b38833 completed April 21, 2026, 12:21 a.m.
Created at: April 16, 2026, 12:42 p.m.