Triple

T32590453
Position Surface form Disambiguated ID Type / Status
Subject Hugh, Duke of Alsace E833049 entity
Predicate nobleTitle P914 FINISHED
Object Duke of Alsace
The Duke of Alsace was a medieval noble title held by regional rulers who governed the historic borderland region of Alsace in what is now eastern France.
E2044283 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: Duke of Alsace | Statement: [Hugh, Duke of Alsace, nobleTitle, Duke of Alsace]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Duke of Alsace
Triple: [Hugh, Duke of Alsace, nobleTitle, Duke of Alsace]
Generated description
The Duke of Alsace was a medieval noble title held by regional rulers who governed the historic borderland region of Alsace in what is now eastern France.

Provenance (5 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_69f34929ff648190aded9424aa7564ae completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c690ad9c8190b81204f8bf7adff0 completed May 3, 2026, 3:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3538eecd1081909dd2a5bf263312ee completed June 19, 2026, 12:41 p.m.
NEDg Description generation batch_6a353992e2c48190b777313293290bad completed June 19, 2026, 12:44 p.m.
NED2 Entity disambiguation (via description) batch_6a353a48a0e08190bbd5d55a8bd390ae completed June 19, 2026, 12:47 p.m.
Created at: May 1, 2026, 1:05 a.m.