Triple

T21314779
Position Surface form Disambiguated ID Type / Status
Subject Reuss-Greiz E525436 entity
Predicate capital P234 FINISHED
Object Greiz 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: Greiz | Statement: [Reuss-Greiz, capital, Greiz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Greiz
Context triple: [Reuss-Greiz, capital, Greiz]
  • A. Greiz chosen
    Greiz is a historic town in eastern Thuringia, Germany, known for its castles and role as a former residence of the Princes of Reuss.
  • B. Altenburg
    Altenburg is a historic town in eastern Thuringia, Germany, known for its playing-card tradition and as the birthplace of the card game Skat.
  • C. Alzenberg
    Alzenberg is a small district or locality that forms part of the town of Calw in the state of Baden-Württemberg, Germany.
  • D. Grezhausen
    Grezhausen is a village-level subdivision of the town of Breisach am Rhein in the state of Baden-Württemberg in southwestern Germany.
  • E. Warstein
    Warstein is a town in North Rhine-Westphalia, Germany, best known for its Warsteiner brewery and its location in the Sauerland region.
  • 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_69e0b51ad810819098c12392c8e55f6c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e75dce6b4081909841ac0440fca5e4 completed April 21, 2026, 11:21 a.m.
Created at: April 16, 2026, 4:28 p.m.