Triple

T12034552
Position Surface form Disambiguated ID Type / Status
Subject Emajõgi River E286500 entity
Predicate passesThrough P225 FINISHED
Object Tartu city centre E43129 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 city centre | Statement: [Emajõgi River, passesThrough, Tartu city centre]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tartu city centre
Context triple: [Emajõgi River, passesThrough, Tartu city centre]
  • A. Tartu chosen
    Tartu is Estonia’s second-largest city and a historic cultural and intellectual center, best known as the country’s main university town.
  • B. Tartu railway station
    Tartu railway station is the main rail transport hub serving the city of Tartu in Estonia, connecting it to other major destinations in the country.
  • C. Tartu Town Hall
    Tartu Town Hall is an 18th-century Baroque-style municipal building and iconic centerpiece of Tartu’s historic town square in Estonia.
  • D. Pärnu
    Pärnu is a coastal city in southwestern Estonia known as a popular summer resort and spa destination on the Baltic Sea.
  • E. Tartu City Council
    Tartu City Council is the elected municipal governing body responsible for setting local policies and overseeing administration in the city of Tartu, Estonia.
  • 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_69d6ab4669e48190b59246358b0383ab completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90408cbf0819093270c9833ef149a completed April 10, 2026, 2:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f5f64826a481908a09ca1c91c4e04f completed May 2, 2026, 1:04 p.m.
Created at: April 8, 2026, 9:47 p.m.