Triple

T31143082
Position Surface form Disambiguated ID Type / Status
Subject Ossory (kingdom) E793842 entity
Predicate ruledBy P3022 FINISHED
Object Dál Birn dynasty
The Dál Birn dynasty was an early medieval Irish royal lineage that provided the kings of Ossory and played a significant role in the politics of southeastern Ireland.
E1974511 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: Dál Birn dynasty | Statement: [Ossory (kingdom), ruledBy, Dál Birn 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: Dál Birn dynasty
Triple: [Ossory (kingdom), ruledBy, Dál Birn dynasty]
Generated description
The Dál Birn dynasty was an early medieval Irish royal lineage that provided the kings of Ossory and played a significant role in the politics of southeastern Ireland.

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_69f224d2b3a48190aa9dd26fbf6eab1a completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f697974e4c819090a4e708a25055d8 completed May 3, 2026, 12:32 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2b84959bd48190a48351f7deef9978 completed June 12, 2026, 4:01 a.m.
NEDg Description generation batch_6a2b8740af048190b5c5abbe045c27f8 completed June 12, 2026, 4:12 a.m.
NED2 Entity disambiguation (via description) batch_6a2b8817aacc8190b2d277720adac752 completed June 12, 2026, 4:16 a.m.
Created at: April 29, 2026, 9:06 p.m.