Triple

T9629377
Position Surface form Disambiguated ID Type / Status
Subject Chesham E232556 entity
Predicate hasTwinTown P919 FINISHED
Object Friedberg, Hesse E347700 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: Friedberg, Hesse | Statement: [Chesham, hasTwinTown, Friedberg, Hesse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Friedberg, Hesse
Context triple: [Chesham, hasTwinTown, Friedberg, Hesse]
  • A. Friedberg, Hesse chosen
    Friedberg, Hesse is a historic town in central Germany’s state of Hesse, known for its medieval architecture and prominent hilltop fortress.
  • B. Friedberg, Germany
    Friedberg, Germany is a historic town in the state of Hesse known for its medieval architecture, including a well-preserved castle and old town center.
  • C. Frankenberg, Hesse
    Frankenberg, Hesse is a small historic town in the German state of Hesse, known for its medieval architecture and location in the Eder river valley.
  • D. Fritzlar
    Fritzlar is a historic town in northern Hesse, Germany, known for its well-preserved medieval old town and its significance in early German Christian history.
  • E. Hanau, Hesse-Kassel
    Hanau, Hesse-Kassel was a historic town and county in the Landgraviate of Hesse-Kassel in what is now central Germany.
  • 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_69ca848793ec8190a93a12383a754dc0 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9b00162481908f396f6b6e470d6c completed April 1, 2026, 10:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69d17987e4008190a8d43641072a1c86 completed April 4, 2026, 8:50 p.m.
Created at: March 30, 2026, 8:10 p.m.