Triple

T36066948
Position Surface form Disambiguated ID Type / Status
Subject O’Beolan family E1043257 entity
Predicate hasAlternativeName P39 FINISHED
Object O’Beolan kindred
The O’Beolan kindred is a medieval Scottish Gaelic family or clan, historically associated with the Highlands and known in various sources under related surname forms.
E2166345 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: O’Beolan kindred | Statement: [O’Beolan family, hasAlternativeName, O’Beolan kindred]
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: O’Beolan kindred
Triple: [O’Beolan family, hasAlternativeName, O’Beolan kindred]
Generated description
The O’Beolan kindred is a medieval Scottish Gaelic family or clan, historically associated with the Highlands and known in various sources under related surname forms.

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_69f76e2fd3248190b900d9a492bf5a7a completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b21808f881908de13f0442f580ef completed May 3, 2026, 8:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38cbac88908190916312c0df9521cd completed June 22, 2026, 5:44 a.m.
NEDg Description generation batch_6a38cc219ad4819081fec325b458005f completed June 22, 2026, 5:46 a.m.
NED2 Entity disambiguation (via description) batch_6a38ccfbece08190be296926289702b2 completed June 22, 2026, 5:49 a.m.
Created at: May 3, 2026, 4:08 p.m.