Triple

T8020366
Position Surface form Disambiguated ID Type / Status
Subject Unstrut River region E186724 entity
Predicate contains P35 FINISHED
Object Memleben E228239 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: Memleben | Statement: [Unstrut River region, contains, Memleben]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Memleben
Context triple: [Unstrut River region, contains, Memleben]
  • A. Memleben chosen
    Memleben is a historic village in Saxony-Anhalt, Germany, notable as a royal palace site of the Ottonian dynasty and the place where Emperor Otto I died.
  • B. Gorcumer
    A Gorcumer is a resident or native of the Dutch city of Gorinchem.
  • C. Maienfeld
    Maienfeld is a historic town in the Swiss canton of Graubünden, best known as the setting of Johanna Spyri’s classic “Heidi” stories.
  • D. Melenki
    Melenki is a small town in western Russia known for its traditional provincial character within the historical region of central European Russia.
  • E. Hernici
    The Hernici were an ancient Italic tribe of central Italy, known for their early alliance and later conflicts with the expanding Roman Republic.
  • 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_69ca82ac7fc081909b1398cf025423af completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3e8d90488190b57d1e748e272061 completed March 31, 2026, 3:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc56c82824819082e93eddc40bfad1 completed March 31, 2026, 11:20 p.m.
Created at: March 30, 2026, 5:20 p.m.