Triple

T23406587
Position Surface form Disambiguated ID Type / Status
Subject John Rayburn E559950 entity
Predicate spouse P13 FINISHED
Object Diana Rayburn
Diana Rayburn is a central character in the television series "Bloodline," known as John Rayburn’s wife who struggles with the growing moral and family conflicts surrounding the Rayburn clan.
E1594871 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: Diana Rayburn | Statement: [John Rayburn, spouse, Diana Rayburn]
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: Diana Rayburn
Triple: [John Rayburn, spouse, Diana Rayburn]
Generated description
Diana Rayburn is a central character in the television series "Bloodline," known as John Rayburn’s wife who struggles with the growing moral and family conflicts surrounding the Rayburn clan.

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_69e2454b3a5881909c64773dc8a5d289 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1a50e607c8190ba0a22e89862a2d9 completed April 29, 2026, 6:28 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f4543c3bc819088d200fd3db69512 completed May 21, 2026, 5:47 p.m.
NEDg Description generation batch_6a0f47d607188190974666bddb39c7cf completed May 21, 2026, 5:58 p.m.
NED2 Entity disambiguation (via description) batch_6a0f484988d081909280fe863dc80e30 completed May 21, 2026, 6 p.m.
Created at: April 17, 2026, 5:38 p.m.