Triple

T2817814
Position Surface form Disambiguated ID Type / Status
Subject Church of Sweden E54332 entity
Predicate headquartersLocation P62 FINISHED
Object Uppsala E36359 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: Uppsala | Statement: [Church of Sweden, headquartersLocation, Uppsala]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Uppsala
Context triple: [Church of Sweden, headquartersLocation, Uppsala]
  • A. Uppsala chosen
    Uppsala is a historic Swedish city north of Stockholm, known for its prestigious university, medieval cathedral, and role as a cultural and ecclesiastical center.
  • B. Sundsvall
    Sundsvall is a coastal city in central Sweden known as an important industrial and commercial center on the Gulf of Bothnia.
  • C. Lund
    Lund is a common Scandinavian surname of Swedish origin.
  • D. Lund
    Lund is a historic city in southern Sweden known for its medieval cathedral, prestigious university, and role as a significant cultural and academic center in Scandinavia.
  • E. Umeå
    Umeå is a university city in northern Sweden known for its cultural scene, research institutions, and role as a regional economic hub.
  • 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_69ab49de0af08190b3da69683be1e728 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abde500d3c8190b435a20a0f9d3b9d completed March 7, 2026, 8:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69b2032ecb7481908801a4896c166203 completed March 12, 2026, 12:05 a.m.
Created at: March 6, 2026, 9:59 p.m.