Triple

T37667268
Position Surface form Disambiguated ID Type / Status
Subject Balliol family E937854 entity
Predicate associatedWithTitle P914 FINISHED
Object Lord of Bywell
Lord of Bywell is a medieval English noble title historically linked to the influential Balliol family, known for its role in Anglo-Scottish aristocracy and kingship.
E2237098 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: Lord of Bywell | Statement: [Balliol family, associatedWithTitle, Lord of Bywell]
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: Lord of Bywell
Triple: [Balliol family, associatedWithTitle, Lord of Bywell]
Generated description
Lord of Bywell is a medieval English noble title historically linked to the influential Balliol family, known for its role in Anglo-Scottish aristocracy and kingship.

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_69f76ed6df7c8190b018e5baea716ceb completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fba9e27d0c81908342e28f016d221a completed May 6, 2026, 8:51 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40ba5cca1881908330d41073559374 completed June 28, 2026, 6:08 a.m.
NEDg Description generation batch_6a40bb14d8288190b392a075de962640 completed June 28, 2026, 6:11 a.m.
NED2 Entity disambiguation (via description) batch_6a40bb99c28881909fe519d20c3fc9c6 completed June 28, 2026, 6:13 a.m.
Created at: May 3, 2026, 4:18 p.m.