Triple

T27665752
Position Surface form Disambiguated ID Type / Status
Subject Owen I of Strathclyde E697222 entity
Predicate positionHeld P8 FINISHED
Object King of Strathclyde
The King of Strathclyde was the monarch of the early medieval Brittonic kingdom of Strathclyde in what is now southern Scotland and northern England.
E672796 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: King of Strathclyde | Statement: [Owen I of Strathclyde, positionHeld, King of Strathclyde]
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: King of Strathclyde
Triple: [Owen I of Strathclyde, positionHeld, King of Strathclyde]
Generated description
The King of Strathclyde was the monarch of the early medieval Brittonic kingdom of Strathclyde in what is now southern Scotland and northern England.

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_69ef590b85a4819083ec7c12bd3c9c10 completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f634a401e08190b2144d47f1df15e0 completed May 2, 2026, 5:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12daa16ebc819083d0165f9beac42f completed May 24, 2026, 11:01 a.m.
NEDg Description generation batch_6a12dbf0cf1c8190bdb81018b840e2d5 completed May 24, 2026, 11:07 a.m.
NED2 Entity disambiguation (via description) batch_6a12dc625e688190a7f2192f3dc53f78 completed May 24, 2026, 11:09 a.m.
Created at: April 27, 2026, 2:38 p.m.