Triple

T7792970
Position Surface form Disambiguated ID Type / Status
Subject Pärnu E180225 entity
Predicate locatedOn P40 FINISHED
Object Pärnu River E194554 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: Pärnu River | Statement: [Pärnu, locatedOn, Pärnu River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Pärnu River
Context triple: [Pärnu, locatedOn, Pärnu River]
  • A. Pärnu River chosen
    The Pärnu River is a major river in southwestern Estonia that flows through the city of Pärnu before emptying into the Gulf of Riga in the Baltic Sea.
  • B. Sustut River
    The Sustut River is a remote river in north-central British Columbia, Canada, known for its wilderness setting and contributions to the Skeena River watershed.
  • C. Jägala River
    The Jägala River is a notable river in northern Estonia known for its scenic Jägala Waterfall before it flows into the Gulf of Finland.
  • D. Lielupe River
    The Lielupe River is a major river in Latvia that flows through the country’s central lowlands before emptying into the Gulf of Riga in the Baltic Sea.
  • E. Narva River
    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.
  • 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_69ca827d22208190b4dc5aa680edcf5d completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cae938714c8190b89917e6ded004da completed March 30, 2026, 9:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69cb13cdb4288190ae3cfe1ee4e3e496 completed March 31, 2026, 12:22 a.m.
Created at: March 30, 2026, 4:31 p.m.