Triple

T36990468
Position Surface form Disambiguated ID Type / Status
Subject Halsey Street station (L) E915081 entity
Predicate hasAdjacentStation P231 FINISHED
Object Wilson Avenue station
Wilson Avenue station is a New York City Subway station on the L line located in the Bushwick neighborhood of Brooklyn.
E2213296 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: Wilson Avenue station | Statement: [Halsey Street station (L), hasAdjacentStation, Wilson Avenue station]
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: Wilson Avenue station
Triple: [Halsey Street station (L), hasAdjacentStation, Wilson Avenue station]
Generated description
Wilson Avenue station is a New York City Subway station on the L line located in the Bushwick neighborhood of Brooklyn.

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_69f76e8dd0408190b8b46da118ea5128 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f9ffdc413c8190a1197d2fc5f1f633 completed May 5, 2026, 2:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3efdac1674819093c1039925982625 completed June 26, 2026, 10:31 p.m.
NEDg Description generation batch_6a3efe555e648190a587f5b1374c95be completed June 26, 2026, 10:33 p.m.
NED2 Entity disambiguation (via description) batch_6a3eff05b5648190baa1d39d59e6d016 completed June 26, 2026, 10:36 p.m.
Created at: May 3, 2026, 4:14 p.m.