Triple

T1960553
Position Surface form Disambiguated ID Type / Status
Subject Nyack, New York, United States of America E42373 entity
Predicate hasZIPCodeTabulationArea P920 FINISHED
Object ZCTA 10960 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: ZCTA 10960 | Statement: [Nyack, New York, United States of America, hasZIPCodeTabulationArea, ZCTA 10960]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasZIPCodeTabulationArea
Context triple: [Nyack, New York, United States of America, hasZIPCodeTabulationArea, ZCTA 10960]
  • A. postalAreaIncludes
    Indicates that a given postal area geographically contains or covers another specified location or region.
  • B. hasAreaCode
    Indicates that a specified telephone area code is assigned to or associated with a particular geographic region, location, or phone service entity.
  • C. postalArea chosen
    Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
  • D. FIPSCode
    Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
  • E. hasCountyCode
    Indicates that an entity is associated with a specific county identified by a standardized county code.
  • F. None of above.

Provenance (3 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_69a8870eea088190a38781990812a9bc completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb68a8e608190bc37a85913b3cd44 completed March 7, 2026, 5:24 a.m.
PD Predicate disambiguation batch_69abaff5dbd48190a9d36ca60de151db completed March 7, 2026, 4:56 a.m.
Created at: March 4, 2026, 7:36 p.m.