Triple

T18456289
Position Surface form Disambiguated ID Type / Status
Subject Oulu sub-region E450909 entity
Predicate namedAfter P63 FINISHED
Object Oulu NE NERFINISHED

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: Oulu | Statement: [Oulu sub-region, namedAfter, Oulu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oulu
Context triple: [Oulu sub-region, namedAfter, Oulu]
  • A. Oulu chosen
    Oulu is a major city in northern Finland known for its technology industry, university, and position near the Gulf of Bothnia.
  • B. Kuopio
    Kuopio is a city in eastern Finland known for its lakeside setting, vibrant cultural life, and status as a regional center for education and commerce.
  • C. Kouvola
    Kouvola is a city in southeastern Finland known as a regional transport hub and gateway to the nearby Repovesi National Park.
  • D. Kokkola
    Kokkola is a coastal city in western Finland known for its maritime heritage and role as a military and naval hub.
  • E. Lahti
    Lahti is a city in southern Finland known for its winter sports facilities, particularly ski jumping and cross-country skiing, and for hosting numerous international sporting events.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d38345688190b565eac2e4cd7935 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5264c10408190b2085ade88655c7d completed April 19, 2026, 7 p.m.
Created at: April 10, 2026, 11:31 a.m.