Triple

T5924694
Position Surface form Disambiguated ID Type / Status
Subject Würzburg E131778 entity
Predicate locatedOnRiver P165 FINISHED
Object Main River E113003 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: Main River | Statement: [Würzburg, locatedOnRiver, Main River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Main River
Context triple: [Würzburg, locatedOnRiver, Main River]
  • A. River Main chosen
    The River Main is a major waterway in central Germany that flows through cities such as Frankfurt before joining the Rhine.
  • B. Sure river
    The Sure river is a Swiss watercourse that drains Lake Sempach and flows through the canton of Lucerne before joining larger river systems.
  • C. Emme River
    The Emme River is a Swiss river flowing through the Emmental region and the Swiss Plateau, known for its picturesque valleys and historical flooding events.
  • D. Current River
    The Current River is a clear, spring-fed river in the Ozarks of southern Missouri and northern Arkansas, popular for canoeing, fishing, and scenic recreation.
  • E. Or River
    The Or River is a waterway in Russia and Kazakhstan that flows through the southern Ural region before joining the Ural River.
  • 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_69c0085b75e88190a632f9691f9da48b completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c03852806c81908ba726c16adf3358 completed March 22, 2026, 6:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0e3a9b6348190909e14e095e2eea0 completed March 23, 2026, 6:54 a.m.
Created at: March 22, 2026, 4 p.m.