Triple

T9275058
Position Surface form Disambiguated ID Type / Status
Subject Tartu railway station E222924 entity
Predicate connectsTo P845 FINISHED
Object Narva E218186 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: Narva | Statement: [Tartu railway station, connectsTo, Narva]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Narva
Context triple: [Tartu railway station, connectsTo, Narva]
  • A. Narva chosen
    Narva is a historic city in northeastern Estonia on the border with Russia, known for its strategic military importance and well-preserved fortress overlooking the Narva River.
  • B. Vasai
    Vasai is a historic coastal town in western India, near Mumbai, known for its strategic importance under Portuguese and later British rule and as the site of the 1802 Treaty of Bassein.
  • C. Kraainem
    Kraainem is a Dutch- and French-speaking suburban municipality on the eastern edge of Brussels in the Flemish Brabant province of Belgium.
  • D. Jelgava
    Jelgava is a city in central Latvia known for its historic Jelgava Palace and role as a regional cultural and educational center.
  • E. Reval
    Reval is the historical German name for Tallinn, the capital city and major port of present-day Estonia on the Baltic Sea.
  • 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_69ca841ffe208190aa7bcffbef2f8379 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd078a045c8190b2c4d1ec64b932ad completed April 1, 2026, 11:54 a.m.
NED1 Entity disambiguation (via context triple) batch_69d121f7a61081908801cdc965f65c3a completed April 4, 2026, 2:36 p.m.
Created at: March 30, 2026, 7:34 p.m.