Triple

T14889663
Position Surface form Disambiguated ID Type / Status
Subject Friedrich Argelander E359718 entity
Predicate workLocation P7 FINISHED
Object Turku E90238 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: Turku | Statement: [Friedrich Argelander, workLocation, Turku]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Turku
Context triple: [Friedrich Argelander, workLocation, Turku]
  • A. Turku chosen
    Turku is one of Finland’s oldest and historically most important cities, located on the southwest coast and known for its medieval heritage and major Baltic Sea port.
  • B. Tampere
    Tampere is a major industrial and cultural city in southern Finland, historically significant as a key battleground in the Finnish Civil War.
  • C. Porvoo
    Porvoo is a historic coastal city in southern Finland known for its well-preserved wooden Old Town and medieval cathedral.
  • D. Helsinki
    Helsinki is the capital and largest city of Finland, known for its coastal location on the Baltic Sea, modern design, and vibrant cultural life.
  • E. Vaasa
    Vaasa is a coastal city in western Finland known for its maritime heritage, bilingual Finnish-Swedish culture, and role as a regional economic and educational center.
  • 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_69d827980cbc8190a0c569ae3940a1d9 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69ded5f6cf5c8190b6b28f58fafe5d59 completed April 15, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a008a1d8e088190a2168952ab5dc687 completed May 10, 2026, 1:37 p.m.
Created at: April 10, 2026, 2:09 a.m.