Triple

T13596009
Position Surface form Disambiguated ID Type / Status
Subject Nitra E324821 entity
Predicate locatedOnRiver P165 FINISHED
Object Nitra River E492393 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: Nitra River | Statement: [Nitra, locatedOnRiver, Nitra River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nitra River
Context triple: [Nitra, locatedOnRiver, Nitra River]
  • A. Nitra River chosen
    The Nitra River is a significant river in western Slovakia that flows through several towns and agricultural regions before joining the Váh River.
  • B. Žitava River
    The Žitava River is a river in southern Slovakia that flows through the Danubian Lowland before joining the Nitra River.
  • C. Opava River
    The Opava River is a significant watercourse in the Czech Republic that flows through the historical region of Silesia, including the city of Opava, before joining the Oder River.
  • D. Brda River
    The Brda River is a significant river in northern Poland that flows through the city of Bydgoszcz and is known for its scenic landscapes and recreational opportunities.
  • E. Hron River
    The Hron River is a major river in central Slovakia that flows through mountainous regions including the Low Tatras before joining the Danube.
  • 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_69d80769eaf081909d82f44e484d6113 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbb0590558819080ccc5874a650b1e completed April 12, 2026, 2:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdfb6e3d048190869bba1b4a7e255f completed May 8, 2026, 3:04 p.m.
Created at: April 9, 2026, 9:49 p.m.