Triple

T36478372
Position Surface form Disambiguated ID Type / Status
Subject borough of Kings County E898734 entity
Predicate isBoroughNumber P186026 FINISHED
Object one of five boroughs of New York City 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: one of five boroughs of New York City | Statement: [borough of Kings County, isBoroughNumber, one of five boroughs of New York City]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isBoroughNumber
Context triple: [borough of Kings County, isBoroughNumber, one of five boroughs of New York City]
  • A. hasBoroughCode
    Indicates that an entity is associated with a specific borough identified by a particular code.
  • B. hasBorough
    Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
  • C. hasBoroughEndpoint
    Indicates that something has an endpoint located within a specific borough.
  • D. hasBoroughEquivalent
    Indicates that one administrative area corresponds functionally or hierarchically to a borough in another jurisdiction or classification system.
  • E. hasBoroughCommunityDistrictCode
    Indicates that a borough is associated with a specific community district code that identifies one of its administrative subdivisions.
  • 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_69f76e5a0e088190a2b6706aeb41723c completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c83f5960819089610ed39c839678 completed May 3, 2026, 10:12 p.m.
PD Predicate disambiguation batch_69f7c477a4d481908f52e55b6688f60c completed May 3, 2026, 9:56 p.m.
PDg Predicate description generation batch_69f7c776b4088190bef550c869da530d completed May 3, 2026, 10:08 p.m.
Created at: May 3, 2026, 4:10 p.m.