Triple

T2360977
Position Surface form Disambiguated ID Type / Status
Subject Elbert E47269 entity
Predicate etymologicalRelation P2530 FINISHED
Object Adalbert E22132 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: Adalbert | Statement: [Elbert, etymologicalRelation, Adalbert]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Adalbert
Context triple: [Elbert, etymologicalRelation, Adalbert]
  • A. Adalbert of Bavaria
    Adalbert of Bavaria was a 19th-century Bavarian prince from the House of Wittelsbach, known for his role in European royal and dynastic affairs.
  • B. Aribert
    Aribert is a Germanic given name, historically borne by medieval nobles and clergy, derived from elements meaning "army" and "bright."
  • C. Adelbert chosen
    Adelbert is a masculine given name of German origin, historically borne by figures such as the poet and naturalist Adelbert von Chamisso.
  • D. Andrew of Galicia
    Andrew of Galicia was a 13th-century prince from the Rurikid dynasty who briefly ruled the Kingdom of Galicia–Volhynia in Eastern Europe.
  • E. Joachim
    Joachim is a masculine given name of Hebrew origin, commonly used in German-speaking and other European countries.
  • 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_69a88a1a4a6081908645b0f2914521ab completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abc723c66481908a9b94991f651b3b completed March 7, 2026, 6:35 a.m.
NED1 Entity disambiguation (via context triple) batch_69aea88cf3308190bdb5aac38aded823 completed March 9, 2026, 11:01 a.m.
Created at: March 4, 2026, 7:55 p.m.