Triple

T35002277
Position Surface form Disambiguated ID Type / Status
Subject Loomis family E1009713 entity
Predicate hasNotableMember P304 FINISHED
Object Abigail Sherwood Loomis
Abigail Sherwood Loomis was a notable member of the Loomis family, recognized for her prominence within this historically significant lineage.
E2133388 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: Abigail Sherwood Loomis | Statement: [Loomis family, hasNotableMember, Abigail Sherwood Loomis]
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: Abigail Sherwood Loomis
Triple: [Loomis family, hasNotableMember, Abigail Sherwood Loomis]
Generated description
Abigail Sherwood Loomis was a notable member of the Loomis family, recognized for her prominence within this historically significant lineage.

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_69f76dcb716881909f75e4fd60ab2284 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f784e6e2e88190abbdd3d261ab8866 completed May 3, 2026, 5:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a380f8d62608190b5a2090ae82ef7a5 completed June 21, 2026, 4:21 p.m.
NEDg Description generation batch_6a3810cbc9d08190bc1360d69f70b6f3 completed June 21, 2026, 4:26 p.m.
NED2 Entity disambiguation (via description) batch_6a3811d3a5c08190b3524a968483243e completed June 21, 2026, 4:31 p.m.
Created at: May 3, 2026, 4:01 p.m.