Triple

T7479506
Position Surface form Disambiguated ID Type / Status
Subject Untermarkt (Görlitz) E176714 entity
Predicate locatedNear P294 FINISHED
Object Neisse River E240507 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: Neisse River | Statement: [Untermarkt (Görlitz), locatedNear, Neisse River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Neisse River
Context triple: [Untermarkt (Görlitz), locatedNear, Neisse River]
  • A. Neisse River chosen
    The Neisse River is a Central European river that forms part of the border between Germany and Poland before joining the Oder River.
  • B. Torsha River
    The Torsha River is a transboundary river flowing through Bhutan and the Indian state of West Bengal, known for its role in irrigation, local ecosystems, and frequent monsoon flooding in the Dooars region.
  • C. Kotorosl River
    The Kotorosl River is a tributary of the Volga in central Russia that flows through the city of Yaroslavl and plays an important role in its landscape and history.
  • D. Salo River
    The Salo River is a watercourse in southwestern Finland that flows through and gives its name to the town of Salo.
  • E. Yèvre River
    The Yèvre River is a waterway in central France that flows through the city of Bourges and forms part of the region’s local river network.
  • 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_69c69f236ce08190a04d7679f03b29b2 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f4f13f548190a8cc59165735b30e completed March 27, 2026, 9:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c941fcac908190a2e9401f136b5f77 completed March 29, 2026, 3:15 p.m.
Created at: March 27, 2026, 3:42 p.m.