Triple

T11955898
Position Surface form Disambiguated ID Type / Status
Subject Kauhava Air Base E284551 entity
Predicate city served P3936 FINISHED
Object Kauhava E289763 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: Kauhava | Statement: [Kauhava Air Base, city served, Kauhava]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kauhava
Context triple: [Kauhava Air Base, city served, Kauhava]
  • A. Kauhava chosen
    Kauhava is a town in western Finland known historically for its aviation activities and air base, as well as its traditional knife-making heritage.
  • B. Vihti
    Vihti is a municipality in southern Finland located within the Uusimaa region, known for its lakes, rural landscapes, and proximity to the Helsinki metropolitan area.
  • C. Raisio
    Raisio is a town and municipality in southwestern Finland known for its industrial base and as the headquarters of the food company Raisio Group.
  • D. Lapua
    Lapua is a small town in western Finland known for its historical significance, including a former state cartridge factory and its role in the Lapua Movement.
  • E. Laakso
    Laakso is a residential district in Helsinki, Finland, known for its green areas and proximity to central neighborhoods like Meilahti.
  • 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_69d6ab2db38c8190b1f0ed6663ef8ada completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90366fda8819083168c93abad27d4 completed April 10, 2026, 2:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69f62a76b0a48190800c5b3cc40308f3 completed May 2, 2026, 4:46 p.m.
Created at: April 8, 2026, 9:45 p.m.