Triple

T24540526
Position Surface form Disambiguated ID Type / Status
Subject Madison, Indiana E607076 entity
Predicate hasHistoricBuilding P1098 FINISHED
Object Sullivan House
Sullivan House is a historic residence in Madison, Indiana, recognized for its architectural and cultural significance within the city's preserved heritage district.
E1638556 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: Sullivan House | Statement: [Madison, Indiana, hasHistoricBuilding, Sullivan House]
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: Sullivan House
Triple: [Madison, Indiana, hasHistoricBuilding, Sullivan House]
Generated description
Sullivan House is a historic residence in Madison, Indiana, recognized for its architectural and cultural significance within the city's preserved heritage district.

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_69e2c4c9bf94819082d05da6f5c29907 completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a8a2f0d88190a3dcc043cb21aaa2 completed April 30, 2026, 12:56 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0feea3fe048190a12255b1be7b5eb8 completed May 22, 2026, 5:50 a.m.
NEDg Description generation batch_6a0fefe9541481909d7dbd79fdf1ef92 completed May 22, 2026, 5:55 a.m.
NED2 Entity disambiguation (via description) batch_6a0ff0cecaf48190951f21afea7a103c completed May 22, 2026, 5:59 a.m.
Created at: April 18, 2026, 2:26 a.m.