Triple

T11207712
Position Surface form Disambiguated ID Type / Status
Subject Narva River E265214 entity
Predicate cityOnRiver P165 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: [Narva River, cityOnRiver, Narva]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Narva
Context triple: [Narva River, cityOnRiver, 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_69d6aac59460819089b9848b27f57848 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8d5f8908190903817f84c629ba1 completed April 9, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4973a1b288190bacdf56f8d4977bd completed April 19, 2026, 8:50 a.m.
Created at: April 8, 2026, 9:30 p.m.