Triple

T1354794
Position Surface form Disambiguated ID Type / Status
Subject Nordic Council E28963 entity
Predicate member P10 FINISHED
Object Åland E23094 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: Åland | Statement: [Nordic Council, member, Åland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Åland
Context triple: [Nordic Council, member, Åland]
  • A. Åland Islands chosen
    The Åland Islands are an autonomous, Swedish-speaking archipelago region of Finland known for their strategic location in the Baltic Sea and extensive self-governance.
  • B. Öland
    Öland is Sweden’s second-largest island, known for its unique limestone plains, rich birdlife, and popular summer tourism along the Baltic Sea coast.
  • C. Gotland
    Gotland is Sweden’s largest island, located in the Baltic Sea and known for its medieval town of Visby, limestone cliffs, and rich Viking-era history.
  • D. Vestland
    Vestland is a county in western Norway known for its dramatic fjords, coastal landscapes, and the city of Bergen.
  • E. Lidingö
    Lidingö is a suburban island town in the Stockholm archipelago known for its affluent residential areas, natural landscapes, and proximity to Sweden’s capital.
  • 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_69a498571d248190a0ac9eb02d97097f completed March 1, 2026, 7:49 p.m.
NER Named-entity recognition batch_69a4c28afc848190925d8b2f9aeac12d completed March 1, 2026, 10:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad01518d5481908cf14b24dde8342b completed March 8, 2026, 4:55 a.m.
Created at: March 1, 2026, 7:56 p.m.