Triple

T16006668
Position Surface form Disambiguated ID Type / Status
Subject Whitneyville, Connecticut E388237 entity
Predicate hasLandmark P105 FINISHED
Object Whitney Avenue
Whitney Avenue is a major thoroughfare in the New Haven, Connecticut area, known for connecting several neighborhoods and serving as a key local commercial and residential corridor.
E1649702 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: Whitney Avenue | Statement: [Whitneyville, Connecticut, hasLandmark, Whitney Avenue]
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: Whitney Avenue
Triple: [Whitneyville, Connecticut, hasLandmark, Whitney Avenue]
Generated description
Whitney Avenue is a major thoroughfare in the New Haven, Connecticut area, known for connecting several neighborhoods and serving as a key local commercial and residential corridor.

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_69d86dabcb7c8190b6a39d6831d2fa1b completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e15800246c8190a298c5f96478c396 completed April 16, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_6a101bc12108819096423d21e6d438a3 completed May 22, 2026, 9:02 a.m.
NEDg Description generation batch_6a102367c6e0819092a483e21fc5cc6c completed May 22, 2026, 9:35 a.m.
NED2 Entity disambiguation (via description) batch_6a10243c77748190a556b0e26d9a2a1c completed May 22, 2026, 9:39 a.m.
Created at: April 10, 2026, 4:55 a.m.