Triple

T12318575
Position Surface form Disambiguated ID Type / Status
Subject Klatovy District E293668 entity
Predicate containsRiver P165 FINISHED
Object Ostružná E470897 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: Ostružná | Statement: [Klatovy District, containsRiver, Ostružná]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ostružná
Context triple: [Klatovy District, containsRiver, Ostružná]
  • A. Ostružná chosen
    Ostružná is a river in the Czech Republic that serves as a tributary of the Úhlava River.
  • B. Ostružnica
    Ostružnica is a suburban neighborhood of Belgrade, Serbia, situated along the Sava River and known for its strategic transport links, including the Ostružnica Bridge.
  • C. Orzola
    Orzola is a small fishing village and port at the northern tip of Lanzarote in the Canary Islands, known as the main departure point for ferries to the nearby island of La Graciosa.
  • D. Vejprnice
    Vejprnice is a municipality and village in the Plzeň Region of the Czech Republic, located just west of the city of Plzeň.
  • E. Chrudimka
    Chrudimka is a river in the Czech Republic that flows through the Pardubice Region and is a tributary of the Elbe.
  • 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_69d6ab6ae0dc8190b1522a9c1c55c114 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d93f4ab1b88190979a8403a430a17c completed April 10, 2026, 6:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69f62a9f708081908c052333c3b7df4c completed May 2, 2026, 4:47 p.m.
Created at: April 8, 2026, 9:53 p.m.