Triple

T34861311
Position Surface form Disambiguated ID Type / Status
Subject John III, Duke of Brabant E1004879 entity
Predicate title P38 FINISHED
Object Duke of Lothier
The Duke of Lothier was a medieval noble title associated with the duchy of Lower Lotharingia in the Holy Roman Empire, often held in conjunction with the Duchy of Brabant.
E436818 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 Lothier | Statement: [John III, Duke of Brabant, title, Duke of Lothier]
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 Lothier
Triple: [John III, Duke of Brabant, title, Duke of Lothier]
Generated description
The Duke of Lothier was a medieval noble title associated with the duchy of Lower Lotharingia in the Holy Roman Empire, often held in conjunction with the Duchy of Brabant.

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_69f76dbb678081909a247b9b5e1a73ac completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78165a57c8190b23fdec518c4f680 completed May 3, 2026, 5:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38cb72d5c081909e1474ce8977616d completed June 22, 2026, 5:43 a.m.
NEDg Description generation batch_6a38cbf4f8b8819093e023e34c71585b completed June 22, 2026, 5:45 a.m.
NED2 Entity disambiguation (via description) batch_6a38cc8927108190977d3dbf2d91f6d2 completed June 22, 2026, 5:47 a.m.
Created at: May 3, 2026, 4 p.m.