Triple

T1816529
Position Surface form Disambiguated ID Type / Status
Subject County of Nassau-Idstein E40447 entity
Predicate namedAfter P63 FINISHED
Object Idstein E224946 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: Idstein | Statement: [County of Nassau-Idstein, namedAfter, Idstein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Idstein
Context triple: [County of Nassau-Idstein, namedAfter, Idstein]
  • A. Idstein chosen
    Idstein is a historic town in the German state of Hesse, known for its well-preserved medieval old town and timber-framed architecture.
  • B. Drensteinfurt
    Drensteinfurt is a small town in North Rhine-Westphalia, Germany, known for its historic architecture and location in the Münsterland region.
  • C. Starnberg
    Starnberg is a lakeside town in Bavaria, Germany, known for its affluent residential character and scenic location on Lake Starnberg southwest of Munich.
  • D. Tureberg
    Tureberg is a central district in Sollentuna Municipality, Sweden, known for housing the municipal center and key public services.
  • E. Essling
    Essling is a village near Vienna, Austria, historically notable as one of the sites of the 1809 Battle of Aspern-Essling during the Napoleonic Wars.
  • 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_69a8864526c081908a3a4d74f689e2c5 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa65f614888190a475f7df627d5f0a completed March 6, 2026, 5:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae26f2c7a48190a091e0e334845413 completed March 9, 2026, 1:48 a.m.
Created at: March 4, 2026, 7:32 p.m.