Triple

T19959595
Position Surface form Disambiguated ID Type / Status
Subject Duke of Arenberg E479775 entity
Predicate dynasticHouse P1547 FINISHED
Object Arenberg 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: Arenberg | Statement: [Duke of Arenberg, dynasticHouse, Arenberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arenberg
Context triple: [Duke of Arenberg, dynasticHouse, Arenberg]
  • A. Arenberg chosen
    Arenberg is a historic town in western Germany that served as the political and administrative center of the former Duchy of Arenberg.
  • B. Arenenberg
    Arenenberg is a historic estate on the shores of Lake Constance in Switzerland, best known as the residence and later death place of Queen Hortense de Beauharnais and a key site of Napoleonic-era history.
  • C. Livarchamps
    Livarchamps is a small village in the municipality of Vaux-sur-Sûre in the Walloon region of Belgium.
  • D. Chavignol
    Chavignol is a small village in France’s Loire Valley renowned for its traditional goat’s milk cheese, Crottin de Chavignol.
  • E. Arroux
    Arroux is a river in central France that flows through the Burgundy region before joining the Loire.
  • 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_69d8e523c19881909f9197037200dde6 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65af386548190aefac1e40aac403d completed April 20, 2026, 4:57 p.m.
Created at: April 10, 2026, 1:54 p.m.