Triple

T38512354
Position Surface form Disambiguated ID Type / Status
Subject Dyckman family E921946 entity
Predicate instanceOf P0 FINISHED
Object New York City notable family C65714 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 notable family
Context triple: [Dyckman family, instanceOf, New York City notable family]
  • A. member of a prominent New York family
    A member of a prominent New York family is an individual born into or formally affiliated with a socially, economically, or politically influential lineage based in New York, whose identity and opportunities are shaped by the family’s status, legacy, and network.
  • B. Hudson River Valley family
    A Hudson River Valley family is a multigenerational household or kinship group rooted in the Hudson River region, whose identity, traditions, and daily life are shaped by the valley’s distinctive history, landscape, and cultural influences.
  • C. New York City connection
    A New York City connection is a relationship, contact, or shared experience that links a person, place, or event to the culture, geography, or social networks of New York City.
  • D. New York City organization
    A New York City organization is an entity—such as a business, nonprofit, government agency, or community group—formally operating within New York City to pursue specific goals, services, or activities.
  • E. New York City community board
    A New York City community board is a local advisory group of appointed residents that consults on land use, budget, and service delivery issues within a specific community district.
  • F. None of above. chosen

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_69f76ea3c5448190aa7002fc1ba3f874 completed May 3, 2026, 3:49 p.m.
Created at: May 3, 2026, 4:32 p.m.