Triple

T6303576
Position Surface form Disambiguated ID Type / Status
Subject Adelsö Church E141314 entity
Predicate locatedIn 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: [Adelsö Church, locatedIn, Uppland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Uppland
Context triple: [Adelsö Church, locatedIn, 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. Dalsland
    Dalsland is a historical province in western Sweden known for its forests, lakes, and rural landscapes.
  • C. Bohuslän
    Bohuslän is a coastal province in western Sweden known for its rugged granite shoreline, fishing villages, and archipelago along the Skagerrak.
  • D. 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.
  • E. Närke
    Närke is a historical province in central Sweden known for its Central Swedish dialects and its location around the city of Örebro.
  • 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_69c008cf0ad4819095def81e2bd42f9f completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0645e150881908b49a07914dcbfd8 completed March 22, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69c71a5cf7008190a24ecfeab5acb583 completed March 28, 2026, 12:01 a.m.
Created at: March 22, 2026, 4:27 p.m.