Triple

T30221567
Position Surface form Disambiguated ID Type / Status
Subject East 105th Street E768356 entity
Predicate hasExitTo P29827 FINISHED
Object Schenck Avenue
Schenck Avenue is a local street in Brooklyn, New York City, running through residential neighborhoods and connecting with nearby thoroughfares such as East 105th Street.
E2294789 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: Schenck Avenue | Statement: [East 105th Street, hasExitTo, Schenck 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: Schenck Avenue
Triple: [East 105th Street, hasExitTo, Schenck Avenue]
Generated description
Schenck Avenue is a local street in Brooklyn, New York City, running through residential neighborhoods and connecting with nearby thoroughfares such as East 105th Street.

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_69f2247fd8b8819087fcf83cb7a05eb8 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6801da3e88190a4862f59160e6832 completed May 2, 2026, 10:52 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7c1ddfe90881909afd1403d78096ab completed Aug. 12, 2026, 7:16 a.m.
NEDg Description generation batch_6a7c1e139f2081909d252f4055a7d3f5 completed Aug. 12, 2026, 7:17 a.m.
NED2 Entity disambiguation (via description) batch_6a7c1ed117208190ac5352f8fb91fd92 completed Aug. 12, 2026, 7:20 a.m.
Created at: April 29, 2026, 7:35 p.m.