Triple

T22314866
Position Surface form Disambiguated ID Type / Status
Subject Battle of Kuortane E551615 entity
Predicate location P40 FINISHED
Object Kuortane 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: Kuortane | Statement: [Battle of Kuortane, location, Kuortane]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kuortane
Context triple: [Battle of Kuortane, location, Kuortane]
  • A. Kuortane chosen
    Kuortane is a rural municipality in western Finland known for its lakeside landscapes and its national sports training center.
  • B. Kinnoul
    Kinnoul is a rural locality within Banana Shire in Queensland, Australia.
  • C. Kopsenni
    Kopsenni is the highest peak on the Faroe Islands' main island of Streymoy, known for its rugged terrain and scenic North Atlantic views.
  • D. Kuisak
    Kuisak is an archaeological site associated with the Bronze Age Sintashta culture, known for its fortified settlements and early chariot burials on the Eurasian steppe.
  • E. Kvam
    Kvam is a municipality in Vestland county, western Norway, known for its scenic location along the Hardangerfjord and traditional fruit farming.
  • 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_69e11e4776588190abb21e5cea79973f completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15751bf208190b8938a00d1afd157 completed April 29, 2026, 12:56 a.m.
Created at: April 16, 2026, 8:42 p.m.