Triple

T35797807
Position Surface form Disambiguated ID Type / Status
Subject Eggertsville E1034884 entity
Predicate hasRoad P959 FINISHED
Object Bailey Avenue
Bailey Avenue is a major thoroughfare in the Buffalo, New York area that runs through the hamlet of Eggertsville and serves as an important local commercial and transit corridor.
E2297173 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: Bailey Avenue | Statement: [Eggertsville, hasRoad, Bailey 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: Bailey Avenue
Triple: [Eggertsville, hasRoad, Bailey Avenue]
Generated description
Bailey Avenue is a major thoroughfare in the Buffalo, New York area that runs through the hamlet of Eggertsville and serves as an important local commercial and transit 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_69f76e169bd081909f16cd8c9ee7870c completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a25600d48190a3b8197343038068 completed May 3, 2026, 7:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a832085d82081909c11ad18f25bc09b completed Aug. 17, 2026, 2:53 p.m.
NEDg Description generation batch_6a8320f1dec88190a16f4a76f3ed8dc0 completed Aug. 17, 2026, 2:55 p.m.
NED2 Entity disambiguation (via description) batch_6a8321a81ed48190bc383b8fc6f3bff9 completed Aug. 17, 2026, 2:58 p.m.
Created at: May 3, 2026, 4:06 p.m.