Triple

T16848322
Position Surface form Disambiguated ID Type / Status
Subject Kuno of Rheinfelden E409602 entity
Predicate familyName P18 FINISHED
Object Rheinfelden E528859 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: Rheinfelden | Statement: [Kuno of Rheinfelden, familyName, Rheinfelden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rheinfelden
Context triple: [Kuno of Rheinfelden, familyName, Rheinfelden]
  • A. Rheinfelden (Aargau)
    Rheinfelden (Aargau) is a historic Swiss town on the Rhine in the canton of Aargau, known as one of the country’s oldest Zähringer-founded cities and a former Habsburg stronghold.
  • B. Riehe
    Riehe is a small river in Lower Saxony, Germany, known as one of the tributaries feeding into the Innerste.
  • C. Rheinsfelden
    Rheinsfelden is a locality in the canton of Zurich, Switzerland, situated near the confluence of the Glatt River with the Rhine.
  • D. Rheinfelden (Baden) chosen
    Rheinfelden (Baden) is a German town in the state of Baden-Württemberg, located on the Rhine near the Swiss border opposite the Swiss town of Rheinfelden.
  • E. Rüthen
    Rüthen is a small historic town in North Rhine-Westphalia, Germany, known for its medieval architecture and location in the scenic Sauerland region.
  • 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_69d883952b048190887740a980b712ed completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b376bac48190ae09f29a28c55f8c completed April 18, 2026, 4:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a018c3489848190869bebedcb5c0564 completed May 11, 2026, 7:58 a.m.
Created at: April 10, 2026, 5:24 a.m.