Triple

T1985513
Position Surface form Disambiguated ID Type / Status
Subject Tartu E43129 entity
Predicate isCountySeatOf P383 FINISHED
Object Tartu County E222912 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: Tartu County | Statement: [Tartu, isCountySeatOf, Tartu County]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tartu County
Context triple: [Tartu, isCountySeatOf, Tartu County]
  • A. Tartu County chosen
    Tartu County is an administrative region in eastern Estonia centered around the university city of Tartu and known for its cultural, educational, and economic significance.
  • B. Harku Parish
    Harku Parish is a rural municipality in northern Estonia, located just west of the capital city Tallinn.
  • C. Suuremõisa
    Suuremõisa is a village on the Estonian island of Hiiumaa, known for its historic manor complex and surrounding park.
  • D. Kuressaare
    Kuressaare is the main town on Estonia’s Saaremaa island, known for its well-preserved medieval castle and seaside spa resort atmosphere.
  • E. Viimsi Parish
    Viimsi Parish is a suburban rural municipality in northern Estonia, located on the Viimsi Peninsula just northeast of the capital city Tallinn.
  • 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_69a88713ddc88190a969715658ebe7a8 completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb821c2d48190abea6c89f37b51b1 completed March 7, 2026, 5:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae0ad53ccc8190b0e0f44cfddfe9a4 completed March 8, 2026, 11:48 p.m.
Created at: March 4, 2026, 7:37 p.m.