Triple

T28124392
Position Surface form Disambiguated ID Type / Status
Subject Pybba of Mercia E710885 entity
Predicate source P409 FINISHED
Object Anglo-Saxon royal genealogies
Anglo-Saxon royal genealogies are early medieval records that trace the lineages of English ruling dynasties, often linking kings to legendary or divine ancestors.
E1803760 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: Anglo-Saxon royal genealogies | Statement: [Pybba of Mercia, source, Anglo-Saxon royal genealogies]
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: Anglo-Saxon royal genealogies
Triple: [Pybba of Mercia, source, Anglo-Saxon royal genealogies]
Generated description
Anglo-Saxon royal genealogies are early medieval records that trace the lineages of English ruling dynasties, often linking kings to legendary or divine ancestors.

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_69ef9b73bd288190a21ae3d6aa14f386 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f640fb767c819088c4253c3ac6739f completed May 2, 2026, 6:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15c935dd908190ab15c54b7162f0f4 completed May 26, 2026, 4:24 p.m.
NEDg Description generation batch_6a15cb20629c81908e81ef6da4f676b1 completed May 26, 2026, 4:32 p.m.
NED2 Entity disambiguation (via description) batch_6a15cbc2fa6c8190a3d8a4b60ab6104c completed May 26, 2026, 4:35 p.m.
Created at: April 27, 2026, 9:19 p.m.