Triple

T12318573
Position Surface form Disambiguated ID Type / Status
Subject Klatovy District E293668 entity
Predicate containsRiver P165 FINISHED
Object Otava E386566 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: Otava | Statement: [Klatovy District, containsRiver, Otava]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Otava
Context triple: [Klatovy District, containsRiver, Otava]
  • A. Otava
    Otava is a major Finnish publishing company known for producing a wide range of literature, non-fiction, and educational materials.
  • B. Otava chosen
    Otava is a major river in the Czech Republic that flows through southwestern Bohemia and is known for its scenic valleys, historical towns, and popularity for canoeing and recreation.
  • C. Sotkamo
    Sotkamo is a municipality in eastern Finland known for its mining industry, outdoor recreation, and the popular Vuokatti ski and sports resort area.
  • D. Kerava
    Kerava is a small city in southern Finland known as a commuter town within the Greater Helsinki region.
  • E. Loviisa
    Loviisa is a small coastal town and municipality in southern Finland known for its historic wooden houses, seaside location, and nuclear power plant.
  • 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_69d6ab6ae0dc8190b1522a9c1c55c114 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d93f4ab1b88190979a8403a430a17c completed April 10, 2026, 6:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff3d3551cc8190848c14c15da07dc4 completed May 9, 2026, 1:57 p.m.
Created at: April 8, 2026, 9:53 p.m.