Triple

T30780555
Position Surface form Disambiguated ID Type / Status
Subject Cusack E783796 entity
Predicate hasNotableBearer P458 FINISHED
Object Raymond Cusack
Raymond Cusack is an individual notable enough to be specifically cited as a bearer of the surname Cusack, though detailed public information about his life or achievements is limited.
E1938837 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: Raymond Cusack | Statement: [Cusack, hasNotableBearer, Raymond Cusack]
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: Raymond Cusack
Triple: [Cusack, hasNotableBearer, Raymond Cusack]
Generated description
Raymond Cusack is an individual notable enough to be specifically cited as a bearer of the surname Cusack, though detailed public information about his life or achievements is limited.

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_69f224b213c8819083886073f90b647e completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f68fe42e448190842c62524baf9abc completed May 2, 2026, 11:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a28e44da3008190b2860db5b9363296 completed June 10, 2026, 4:13 a.m.
NEDg Description generation batch_6a28e86225188190a5aa53d9baa03bcc completed June 10, 2026, 4:30 a.m.
NED2 Entity disambiguation (via description) batch_6a28e8c7896c81909d9549c47419c25f completed June 10, 2026, 4:32 a.m.
Created at: April 29, 2026, 8:41 p.m.