Triple

T9173753
Position Surface form Disambiguated ID Type / Status
Subject Kronberg im Taunus E220143 entity
Predicate hasCityPart P12399 FINISHED
Object Kronberg E220143 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: Kronberg | Statement: [Kronberg im Taunus, hasCityPart, Kronberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kronberg
Context triple: [Kronberg im Taunus, hasCityPart, Kronberg]
  • A. Kronberg im Taunus chosen
    Kronberg im Taunus is a historic, affluent town near Frankfurt in the Taunus mountains of Hesse, Germany, known for its medieval old town, castle, and role as a residential and resort community.
  • B. Kronsberg
    Kronsberg is a location in Germany known, among other things, as the place where former Nazi youth leader Baldur von Schirach died.
  • C. Günsberg
    Günsberg is a Swiss municipality located in the canton of Solothurn, known for its scenic setting near the Jura Mountains.
  • D. Plüderhausen
    Plüderhausen is a municipality in the German state of Baden-Württemberg, located in the Rems Valley east of Stuttgart.
  • E. Kransberg
    Kransberg is a village and district of the town of Usingen in the Hochtaunus region of Hesse, 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_69ca83e467108190abcae6a33b3d4dad completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccbfa128d48190b54b8f95d77d81cc completed April 1, 2026, 6:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1610abbec81908743c1ef20fb39d4 completed April 4, 2026, 7:05 p.m.
Created at: March 30, 2026, 7:22 p.m.