Triple

T15714724
Position Surface form Disambiguated ID Type / Status
Subject Region of Uusimaa E380931 entity
Predicate contains P35 FINISHED
Object Kerava 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: Kerava | Statement: [Region of Uusimaa, contains, Kerava]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kerava
Context triple: [Region of Uusimaa, contains, Kerava]
  • A. Kerava chosen
    Kerava is a small city in southern Finland known as a commuter town within the Greater Helsinki region.
  • B. Kirkee
    Kirkee is a cantonment town near Pune in Maharashtra, India, historically notable as the site of a major Anglo-Maratha War battle.
  • C. Imatra
    Imatra is a town and municipality in southeastern Finland known for its industrial history, proximity to the Russian border, and the Imatrankoski rapids.
  • D. Kouvola
    Kouvola is a city in southeastern Finland known as a regional transport hub and gateway to the nearby Repovesi National Park.
  • E. Savukoski
    Savukoski is a sparsely populated municipality in Finnish Lapland known for its vast wilderness areas and traditional reindeer herding culture.
  • 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_69d86d9bf930819082b30cf6d169297c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e04f90aea0819082a9e9fe0f7780b0 completed April 16, 2026, 2:55 a.m.
Created at: April 10, 2026, 4:45 a.m.