Triple

T35030816
Position Surface form Disambiguated ID Type / Status
Subject Conrad, Duke of Rothenburg E1010474 entity
Predicate title P38 FINISHED
Object Duke of Rothenburg
Duke of Rothenburg was a medieval German noble title held by Conrad, associated with the region around the town of Rothenburg.
E2137194 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 Rothenburg | Statement: [Conrad, Duke of Rothenburg, title, Duke of Rothenburg]
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 Rothenburg
Triple: [Conrad, Duke of Rothenburg, title, Duke of Rothenburg]
Generated description
Duke of Rothenburg was a medieval German noble title held by Conrad, associated with the region around the town of Rothenburg.

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_69f76dccf0108190af43b465d3750196 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f785468bc88190bece118c6e900400 completed May 3, 2026, 5:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3823ac54808190bfa2bc110176afef completed June 21, 2026, 5:47 p.m.
NEDg Description generation batch_6a3824823190819085d090f2dbb608f9 completed June 21, 2026, 5:50 p.m.
NED2 Entity disambiguation (via description) batch_6a38266c9a8c81908c041eab45f05c6f completed June 21, 2026, 5:59 p.m.
Created at: May 3, 2026, 4:01 p.m.