Triple

T13453178
Position Surface form Disambiguated ID Type / Status
Subject Duke of Leuchtenberg E311161 entity
Predicate namedAfter P63 FINISHED
Object Leuchtenberg E809590 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: Leuchtenberg | Statement: [Duke of Leuchtenberg, namedAfter, Leuchtenberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leuchtenberg
Context triple: [Duke of Leuchtenberg, namedAfter, Leuchtenberg]
  • A. Leuchtenberg chosen
    Leuchtenberg is a small municipality in Bavaria, Germany, known for its historic hilltop castle ruins and scenic Upper Palatinate countryside.
  • B. Lunzenau
    Lunzenau is a small town in the German state of Saxony, known for its location along the Zwickauer Mulde river and its historic architecture.
  • C. Luxenberg
    Luxenberg is an alternative spelling or variant form of the name "Luxemburg," which can refer to the European country Luxembourg or the surname of notable individuals such as revolutionary Rosa Luxemburg.
  • D. Leuenberg
    Leuenberg is a village in Switzerland known as the site where major European Protestant churches concluded the Leuenberg Agreement on church fellowship.
  • E. Fürstenau
    Fürstenau is a village and district within the town of Höxter in North Rhine-Westphalia, 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_69d806a938b8819097ec43a2229fc7f9 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaefae85481909e6a59797cbb25e7 completed April 12, 2026, 2:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f77f7dcb8481909299419234dd30fe completed May 3, 2026, 5:01 p.m.
Created at: April 9, 2026, 9:41 p.m.