Triple

T31625909
Position Surface form Disambiguated ID Type / Status
Subject Henry of Speyer E807022 entity
Predicate residence P75 FINISHED
Object Speyergau
Speyergau was a medieval county in the region around the city of Speyer in present-day southwestern Germany, historically associated with various noble families of the Holy Roman Empire.
E1988085 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: Speyergau | Statement: [Henry of Speyer, residence, Speyergau]
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: Speyergau
Triple: [Henry of Speyer, residence, Speyergau]
Generated description
Speyergau was a medieval county in the region around the city of Speyer in present-day southwestern Germany, historically associated with various noble families of the Holy Roman Empire.

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_69f348d7883c8190b6c13ab92b7ef076 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a8dfcc708190b19e7444a14cdbb9 completed May 3, 2026, 1:46 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2ed4c8c3f48190933b5e0cc796d7ec completed June 14, 2026, 4:20 p.m.
NEDg Description generation batch_6a2ed55fcd2c8190a2168167792d253d completed June 14, 2026, 4:22 p.m.
NED2 Entity disambiguation (via description) batch_6a2ed6052b008190a0f55e32f516645c completed June 14, 2026, 4:25 p.m.
Created at: April 30, 2026, 10:43 p.m.