Triple

T21366159
Position Surface form Disambiguated ID Type / Status
Subject Ellen Spencer Mussey E526919 entity
Predicate spouse P13 FINISHED
Object Reuben D. Mussey Jr.
Reuben D. Mussey Jr. was a 19th-century American lawyer, Civil War officer, and later a prominent Washington, D.C. attorney known for his legal and political work.
E2289397 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: Reuben D. Mussey Jr. | Statement: [Ellen Spencer Mussey, spouse, Reuben D. Mussey Jr.]
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: Reuben D. Mussey Jr.
Triple: [Ellen Spencer Mussey, spouse, Reuben D. Mussey Jr.]
Generated description
Reuben D. Mussey Jr. was a 19th-century American lawyer, Civil War officer, and later a prominent Washington, D.C. attorney known for his legal and political work.

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_69e0b51d8a308190b09113b3b3f9bc15 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b06fbe108190a07a46824b96a963 completed April 22, 2026, 11:26 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5b302f3030819080d8ebfd82702948 completed July 18, 2026, 7:50 a.m.
NEDg Description generation batch_6a5b316b28d4819095b7ec485bfe39df completed July 18, 2026, 7:55 a.m.
NED2 Entity disambiguation (via description) batch_6a5b33704d508190af060d1dae5e487b completed July 18, 2026, 8:04 a.m.
Created at: April 16, 2026, 5:09 p.m.