Triple

T28463300
Position Surface form Disambiguated ID Type / Status
Subject 182nd–183rd Streets (IND Concourse Line) E720218 entity
Predicate hasExitTo P29827 FINISHED
Object East 182nd Street
East 182nd Street is a roadway in the Bronx, New York City, that serves as a local thoroughfare and is accessible via nearby subway stations.
E1948244 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: East 182nd Street | Statement: [182nd–183rd Streets (IND Concourse Line), hasExitTo, East 182nd Street]
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: East 182nd Street
Triple: [182nd–183rd Streets (IND Concourse Line), hasExitTo, East 182nd Street]
Generated description
East 182nd Street is a roadway in the Bronx, New York City, that serves as a local thoroughfare and is accessible via nearby subway stations.

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_69f01a58a67c819097936d9e8da8d6e6 completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f64ea7a0b48190ae49504aad5b375b completed May 2, 2026, 7:21 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2946f890948190825d8feec5cc7055 completed June 10, 2026, 11:14 a.m.
NEDg Description generation batch_6a29481984b88190ae3ff50867361a83 completed June 10, 2026, 11:18 a.m.
NED2 Entity disambiguation (via description) batch_6a2948e754b8819086933f825367a373 completed June 10, 2026, 11:22 a.m.
Created at: April 28, 2026, 2:42 a.m.