Triple

T33541047
Position Surface form Disambiguated ID Type / Status
Subject Thuringian states E859071 entity
Predicate hasPart P35 FINISHED
Object Principality of Reuss-Greiz
The Principality of Reuss-Greiz was a small historical German state ruled by the Reuss family, located in what is now the federal state of Thuringia.
E330017 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: Principality of Reuss-Greiz | Statement: [Thuringian states, hasPart, Principality of Reuss-Greiz]
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: Principality of Reuss-Greiz
Triple: [Thuringian states, hasPart, Principality of Reuss-Greiz]
Generated description
The Principality of Reuss-Greiz was a small historical German state ruled by the Reuss family, located in what is now the federal state of Thuringia.

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_69f3497a5be08190a39b12736899e034 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6f6c442d48190ab01d16363ea1b3f completed May 3, 2026, 7:18 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3740e927a88190a5879a1c116afa5b completed June 21, 2026, 1:39 a.m.
NEDg Description generation batch_6a374208897081909434c3a2e34d2d2f completed June 21, 2026, 1:44 a.m.
NED2 Entity disambiguation (via description) batch_6a37432ea1e881909dbfe25e33f6c6fa completed June 21, 2026, 1:49 a.m.
Created at: May 1, 2026, 1:39 a.m.