Triple

T18956059
Position Surface form Disambiguated ID Type / Status
Subject Sorau E463783 entity
Predicate hasGermanName P1435 FINISHED
Object Sorau NE NERFINISHED

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: Sorau | Statement: [Sorau, hasGermanName, Sorau]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sorau
Context triple: [Sorau, hasGermanName, Sorau]
  • A. Sorau chosen
    Sorau is a historic town in present-day Żary, western Poland, that was formerly part of Prussia and is known for its shifting political affiliations in Central European history.
  • B. Sinnar
    Sinnar is a town in the Nashik district of Maharashtra, India, known for its historical temples and growing industrial development.
  • C. Sa’och
    Sa’och is an indigenous Pearic language (and its associated ethnic group) of mainland Southeast Asia, traditionally spoken by a small community in Cambodia and nearby regions.
  • D. Harestua
    Harestua is a village in Viken county, Norway, known for its residential community and proximity to the Harestua Solar Observatory.
  • E. Suhre
    The Suhre is a river in Switzerland that flows through the cantons of Lucerne and Aargau before joining the Aare.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8dcffc278819086792a4ebfddfafa completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d5cdf2d08190a0aecd3fa5335a75 completed April 20, 2026, 7:29 a.m.
Created at: April 10, 2026, noon