Triple

T27912449
Position Surface form Disambiguated ID Type / Status
Subject Hamden High School E705968 entity
Predicate governingBody P46 FINISHED
Object Hamden Public Schools
Hamden Public Schools is the public school district serving the town of Hamden, Connecticut, overseeing Hamden High School and its other local schools.
E1794143 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: Hamden Public Schools | Statement: [Hamden High School, governingBody, Hamden Public Schools]
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: Hamden Public Schools
Triple: [Hamden High School, governingBody, Hamden Public Schools]
Generated description
Hamden Public Schools is the public school district serving the town of Hamden, Connecticut, overseeing Hamden High School and its other local schools.

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_69ef96b5aad08190be36a277c31e7004 completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69f63a270d648190aca6df6ee7f6014d completed May 2, 2026, 5:53 p.m.
NED1 Entity disambiguation (via context triple) batch_6a13037077448190b5bcbef3bc7682c4 completed May 24, 2026, 1:56 p.m.
NEDg Description generation batch_6a1303fd53888190856a4b6e2b5f5dd5 completed May 24, 2026, 1:58 p.m.
NED2 Entity disambiguation (via description) batch_6a1304b2a0c481909283b9cafea6b075 completed May 24, 2026, 2:01 p.m.
Created at: April 27, 2026, 6:51 p.m.