Triple

T23218527
Position Surface form Disambiguated ID Type / Status
Subject Kurpfalz E580817 entity
Predicate hasCity P316 FINISHED
Object Ladenburg NE NERFINISHED

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: Ladenburg | Statement: [Kurpfalz, hasCity, Ladenburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ladenburg
Context triple: [Kurpfalz, hasCity, Ladenburg]
  • A. Ladenburg chosen
    Ladenburg is a historic town in southwestern Germany known for its well-preserved old town and its association with automobile pioneer Karl Benz.
  • B. Löwenthal
    Löwenthal is the maiden surname of Elsa Einstein, who was both the second wife and cousin of physicist Albert Einstein.
  • C. Friedberg
    Friedberg is a German-origin surname borne by various notable individuals across fields such as landscape architecture, academia, and the arts.
  • D. Friedberg
    Friedberg is a historic German town in the state of Hesse, known for its medieval fortifications and strategic importance during the Seven Years' War.
  • E. Berkheim
    Berkheim is a small municipality in the district of Biberach in the federal state of Baden-Württemberg in southern Germany.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e2460389408190be74f41d217799a9 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1916653f08190a7dcbc659c6b6a25 completed April 29, 2026, 5:04 a.m.
Created at: April 17, 2026, 4:08 p.m.