Triple

T1025605
Position Surface form Disambiguated ID Type / Status
Subject Adelbert E22132 entity
Predicate relatedName P3889 FINISHED
Object Adelbrecht E73267 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: Adelbrecht | Statement: [Adelbert, relatedName, Adelbrecht]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Adelbrecht
Context triple: [Adelbert, relatedName, Adelbrecht]
  • A. Aribert
    Aribert is a Germanic given name, historically borne by medieval nobles and clergy, derived from elements meaning "army" and "bright."
  • B. Albrecht chosen
    Albrecht is a Germanic given name, historically borne by various nobles, artists, and scholars in German-speaking Europe.
  • C. Eberhard
    Eberhard is a German masculine given name of Old High German origin, traditionally meaning "strong boar" or "brave boar."
  • D. Ruprecht
    Ruprecht is a German given name, cognate with Robert, traditionally borne by various historical figures and saints in German-speaking regions.
  • E. Otto the Illustrious
    Otto the Illustrious was a powerful 9th–10th century German nobleman of the Liudolfing dynasty whose rule and lineage laid the groundwork for the rise of the Ottonian Holy Roman Emperors.
  • 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_69a493d6e380819097b384986ffc315c completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b7f4c66c8190b6098fb72c1465a3 completed March 1, 2026, 10:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac6f0781e08190bbfd5fad2b122150 completed March 7, 2026, 6:31 p.m.
Created at: March 1, 2026, 7:41 p.m.