Triple

T8258266
Position Surface form Disambiguated ID Type / Status
Subject Astoria waterfront redevelopment E193123 entity
Predicate landUseChangeTo P81240 FINISHED
Object mixed-use residential and commercial LITERAL 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: mixed-use residential and commercial | Statement: [Astoria waterfront redevelopment, landUseChangeTo, mixed-use residential and commercial]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: landUseChangeTo
Context triple: [Astoria waterfront redevelopment, landUseChangeTo, mixed-use residential and commercial]
  • A. formerLandUse
    Indicates the type of land use that characterized a location prior to its current or present use.
  • B. otherLandUse
    Indicates that the land is used for purposes that do not fall into any of the primary or predefined land-use categories.
  • C. landUseContext
    Indicates the contextual setting or circumstances under which a particular piece of land is used or designated for a specific purpose.
  • D. majorLandUse
    Indicates the primary way a given area of land is utilized or designated (e.g., residential, commercial, agricultural).
  • E. landUseIncludes
    Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
  • F. None of above. chosen

Provenance (4 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_69ca82dfad9c8190b8cd18fb89f50f40 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb78fce9308190ac36512e80b06b52 completed March 31, 2026, 7:34 a.m.
PD Predicate disambiguation batch_69cb36b6d5548190b665a6cce14c69f7 completed March 31, 2026, 2:51 a.m.
PDg Predicate description generation batch_69cb44d1caa881909069fa925a91316b completed March 31, 2026, 3:51 a.m.
Created at: March 30, 2026, 5:49 p.m.