Triple

T38147564
Position Surface form Disambiguated ID Type / Status
Subject Eadberht I of Kent E952659 entity
Predicate coRuledWith P13111 FINISHED
Object Æðelberht II of Kent
Æðelberht II of Kent was an 8th-century Anglo-Saxon king of Kent known for his joint rule and involvement in the complex dynastic politics of the period.
E1706282 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: Æðelberht II of Kent | Statement: [Eadberht I of Kent, coRuledWith, Æðelberht II of Kent]
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: Æðelberht II of Kent
Triple: [Eadberht I of Kent, coRuledWith, Æðelberht II of Kent]
Generated description
Æðelberht II of Kent was an 8th-century Anglo-Saxon king of Kent known for his joint rule and involvement in the complex dynastic politics of the period.

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_69f76f0a67f4819080c492f61d688fcc completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fc46103ff48190b981d147997e4c85 completed May 7, 2026, 7:58 a.m.
NED1 Entity disambiguation (via context triple) batch_6a42458f9b488190bcb5eda521b43707 completed June 29, 2026, 10:14 a.m.
NEDg Description generation batch_6a424663f1c481909dc832d8484c6447 completed June 29, 2026, 10:18 a.m.
NED2 Entity disambiguation (via description) batch_6a4246b4a8208190bdf87ace5e912e82 completed June 29, 2026, 10:19 a.m.
Created at: May 3, 2026, 4:21 p.m.