Triple
T29843590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Comprehensive Waterfront Plan |
E757867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New York City government policy document |
C53975
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: New York City government policy document Context triple: [New York City Comprehensive Waterfront Plan, instanceOf, New York City government policy document]
-
A.
New York City government publication
chosen
A New York City government publication is an official document or media issued by a NYC governmental agency or office to communicate information, policies, data, or services to the public or other stakeholders.
-
B.
New York City government procedure
A New York City government procedure is a formally defined, legally compliant sequence of steps and requirements through which city agencies and officials carry out public functions, make decisions, or deliver services to residents and businesses.
-
C.
New York State government document
A New York State government document is an official record, publication, or communication produced or issued by an agency, department, or office of the New York State government in the course of its public duties.
-
D.
New York City agency
A New York City agency is a governmental organization responsible for administering and enforcing specific public services, regulations, and policies within the five boroughs of New York City.
-
E.
New York City program
A New York City program is an organized, city-sanctioned initiative or service designed to address specific public needs or policy goals within the five boroughs.
- F. None of above.
Provenance (1 batch)
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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:40 p.m.