Triple

T10108738
Position Surface form Disambiguated ID Type / Status
Subject Narva E218186 entity
Predicate borderRiver P224 FINISHED
Object Narva River E265214 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 River | Statement: [Narva, borderRiver, Narva River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Narva River
Context triple: [Narva, borderRiver, Narva River]
  • A. Narva River chosen
    The Narva River is a major river in northeastern Europe that forms part of the border between Estonia and Russia, flowing from Lake Peipus into the Baltic Sea.
  • B. Daugava River
    The Daugava River is a major Eastern European river flowing through Russia, Belarus, and Latvia before emptying into the Baltic Sea.
  • C. Gołdapa River
    The Gołdapa River is a watercourse in northeastern Poland that flows through the town of Gołdap before joining larger regional river systems.
  • D. Onega River
    The Onega River is a major river in northwestern Russia that flows through the Karelia region before emptying into the White Sea.
  • E. Western Dvina River
    The Western Dvina River, also known as the Daugava, is a major Eastern European river flowing from Russia through Belarus and Latvia into 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_69ca83da93fc8190b54e44bc2b34857c completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cdd0cbd8a48190b2af6177d1249f58 completed April 2, 2026, 2:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69d3005e007881909f40575d129f2c3d completed April 6, 2026, 12:37 a.m.
Created at: March 30, 2026, 9:03 p.m.