Triple

T31831603
Position Surface form Disambiguated ID Type / Status
Subject Principality of Leiningen E812551 entity
Predicate rulingDynasty P1547 FINISHED
Object Leiningen dynasty
The Leiningen dynasty is a historic German noble family that held significant territorial power and influence in the Holy Roman Empire and later German states.
E1982029 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: Leiningen dynasty | Statement: [Principality of Leiningen, rulingDynasty, Leiningen dynasty]
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: Leiningen dynasty
Triple: [Principality of Leiningen, rulingDynasty, Leiningen dynasty]
Generated description
The Leiningen dynasty is a historic German noble family that held significant territorial power and influence in the Holy Roman Empire and later German states.

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_69f348ea7ffc8190a2ab43d80277cf59 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6af898f748190a7f3dbb51959233a completed May 3, 2026, 2:14 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2e7fd04efc819096a19fdffed4ea62 completed June 14, 2026, 10:17 a.m.
NEDg Description generation batch_6a2e80de968881909cc569b5791a9b1c completed June 14, 2026, 10:22 a.m.
NED2 Entity disambiguation (via description) batch_6a2e819a4f6881908d80b523aa9bd753 completed June 14, 2026, 10:25 a.m.
Created at: April 30, 2026, 11:47 p.m.