Triple

T34401628
Position Surface form Disambiguated ID Type / Status
Subject Glen Oaks, Queens E882992 entity
Predicate hasHousingDevelopment P40332 FINISHED
Object Glen Oaks Village
Glen Oaks Village is a large post–World War II garden apartment cooperative community located in the Glen Oaks neighborhood of Queens, New York City.
E2095266 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: Glen Oaks Village | Statement: [Glen Oaks, Queens, hasHousingDevelopment, Glen Oaks Village]
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: Glen Oaks Village
Triple: [Glen Oaks, Queens, hasHousingDevelopment, Glen Oaks Village]
Generated description
Glen Oaks Village is a large post–World War II garden apartment cooperative community located in the Glen Oaks neighborhood of Queens, New York City.

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_69f349c1304081909331872829e38106 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7189a76508190a5b1c1204915fc8a completed May 3, 2026, 9:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a370dcbeb9c8190bbf66e26331779b9 completed June 20, 2026, 10:01 p.m.
NEDg Description generation batch_6a370e7f2e6c8190858406dcdcdaafb7 completed June 20, 2026, 10:04 p.m.
NED2 Entity disambiguation (via description) batch_6a370f0b3e5c8190a74b88ad1ba900ea completed June 20, 2026, 10:07 p.m.
Created at: May 1, 2026, 1:59 a.m.