Triple

T12485543
Position Surface form Disambiguated ID Type / Status
Subject Prince of Eichstätt E298422 entity
Predicate locatedIn P40 FINISHED
Object Eichstätt E680543 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: Eichstätt | Statement: [Prince of Eichstätt, locatedIn, Eichstätt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eichstätt
Context triple: [Prince of Eichstätt, locatedIn, Eichstätt]
  • A. Eichstätt chosen
    Eichstätt is a historic Bavarian town in southern Germany known for its baroque architecture, Catholic university, and location within the Altmühltal Nature Park.
  • B. Rosenheim
    Rosenheim is a town in Upper Bavaria, Germany, known as a regional economic and transportation hub near the Alps.
  • C. Traunstein
    Traunstein is a town in southeastern Bavaria, Germany, known as a regional administrative and cultural center near the Chiemsee and the Alps.
  • D. Kaufbeuren
    Kaufbeuren is a historic Bavarian town in southern Germany known for its well-preserved medieval old town and traditional Swabian culture.
  • E. Straubing
    Straubing is a Bavarian town on the Danube River known for its historic city center and role as a regional economic and educational hub.
  • 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_69d6ada377208190a36011199a4d8558 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94ddf0b6c8190aff4fe267d8f6efe completed April 10, 2026, 7:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd3cf630a8819094455fc45a815b83 completed May 8, 2026, 1:31 a.m.
Created at: April 8, 2026, 9:56 p.m.