Triple

T5130465
Position Surface form Disambiguated ID Type / Status
Subject Rijeka E115683 entity
Predicate historicalName P65 FINISHED
Object Reka E445572 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: Reka | Statement: [Rijeka, historicalName, Reka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Reka
Context triple: [Rijeka, historicalName, Reka]
  • A. Bes River
    The Bes River is a regional river in central India that flows near the city of Vidisha in Madhya Pradesh.
  • B. Kupa River chosen
    The Kupa River is a central European river flowing through Croatia and Slovenia, known for passing through cities like Karlovac and forming part of the Croatia–Slovenia border.
  • C. Körös
    Körös is a river in Central Europe that flows through eastern Hungary and parts of Romania before joining the Tisza River.
  • D. Bega River
    The Bega River is a waterway in southeastern New South Wales, Australia, that flows through the town of Bega before reaching the Tasman Sea.
  • E. Dyje
    The Dyje is a major river in Central Europe that flows through the Czech Republic and Austria, forming part of their border and contributing significantly to the Morava River basin.
  • 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_69bd444426bc819099ccd23f141e22aa completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd7827c764819086da3b79f2020224 completed March 20, 2026, 4:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf10ba84d88190babe5d9f676ba7b6 completed March 21, 2026, 9:42 p.m.
Created at: March 20, 2026, 1:42 p.m.