Triple

T16906567
Position Surface form Disambiguated ID Type / Status
Subject Helgö E424578 entity
Predicate locatedInRegion P40 FINISHED
Object Uppland E110264 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: Uppland | Statement: [Helgö, locatedInRegion, Uppland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Uppland
Context triple: [Helgö, locatedInRegion, Uppland]
  • A. Uppland chosen
    Uppland is a historical province in east-central Sweden that includes parts of the greater Stockholm area and key infrastructure such as Stockholm Arlanda Airport.
  • B. Södermanland
    Södermanland is a historical province in eastern Sweden, located south of Lake Mälaren and west of the Baltic Sea, known for its castles, lakes, and early Swedish cultural heritage.
  • C. Dalsland
    Dalsland is a historical province in western Sweden known for its forests, lakes, and rural landscapes.
  • D. Bohuslän
    Bohuslän is a coastal province in western Sweden known for its rugged granite shoreline, fishing villages, and archipelago along the Skagerrak.
  • E. Botkyrka region
    The Botkyrka region is a municipality in Stockholm County, Sweden, known for its cultural diversity and historical association with the medieval saint Botvid.
  • 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_69d889da3e8c8190a2b118f383f0beac completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e3ca39f9b08190b15106c6caf895ec completed April 18, 2026, 6:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c7b7b698819081d2e39976b69587 completed May 10, 2026, 6 p.m.
Created at: April 10, 2026, 5:30 a.m.