Triple

T35596922
Position Surface form Disambiguated ID Type / Status
Subject Maegor I Targaryen E1028657 entity
Predicate spouse P13 FINISHED
Object Ceryse Hightower
Ceryse Hightower was a noblewoman of House Hightower who became queen consort of Westeros through her politically significant but troubled marriage to King Maegor I Targaryen.
E2156076 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: Ceryse Hightower | Statement: [Maegor I Targaryen, spouse, Ceryse Hightower]
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: Ceryse Hightower
Triple: [Maegor I Targaryen, spouse, Ceryse Hightower]
Generated description
Ceryse Hightower was a noblewoman of House Hightower who became queen consort of Westeros through her politically significant but troubled marriage to King Maegor I Targaryen.

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_69f76e0598dc8190a6a093e904b9aa70 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79ea94cd88190a4ce214b1343ff0f completed May 3, 2026, 7:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38914dc2a4819082b8d704c262f72c completed June 22, 2026, 1:35 a.m.
NEDg Description generation batch_6a38922d9814819089669865036c8474 completed June 22, 2026, 1:38 a.m.
NED2 Entity disambiguation (via description) batch_6a3892ae3d608190b6594f287fa7ff6d completed June 22, 2026, 1:41 a.m.
Created at: May 3, 2026, 4:05 p.m.