Triple

T8371128
Position Surface form Disambiguated ID Type / Status
Subject Regierungsbezirk Tübingen E197455 entity
Predicate containsAdministrativeTerritorialEntity P747 FINISHED
Object Pfullendorf E527602 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: Pfullendorf | Statement: [Regierungsbezirk Tübingen, containsAdministrativeTerritorialEntity, Pfullendorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pfullendorf
Context triple: [Regierungsbezirk Tübingen, containsAdministrativeTerritorialEntity, Pfullendorf]
  • A. Pfullendorf chosen
    Pfullendorf is a historic town in the state of Baden-Württemberg in southern Germany, known for its well-preserved medieval old town.
  • B. Lülsfeld
    Lülsfeld is a small municipality in the Schweinfurt district of Lower Franconia in northern Bavaria, Germany.
  • C. Pennenfeld
    Pennenfeld is a residential subdistrict of the Bonn borough of Bad Godesberg in Germany.
  • D. Günsberg
    Günsberg is a Swiss municipality located in the canton of Solothurn, known for its scenic setting near the Jura Mountains.
  • E. Weiterstadt
    Weiterstadt is a town in the German state of Hesse, located near Darmstadt and known for its residential areas and commercial centers.
  • 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_69ca82f56730819080cec5d991c76f4c completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb80a509dc81909e0ea4c66b21d84f completed March 31, 2026, 8:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69cf422648208190beaa6eaef4173f21 completed April 3, 2026, 4:29 a.m.
Created at: March 30, 2026, 6:01 p.m.