Triple

T25048965
Position Surface form Disambiguated ID Type / Status
Subject Town of Ancram, New York E627322 entity
Predicate isInHudsonRiverWatershed P17416 FINISHED
Object true 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: true | Statement: [Town of Ancram, New York, isInHudsonRiverWatershed, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInHudsonRiverWatershed
Context triple: [Town of Ancram, New York, isInHudsonRiverWatershed, true]
  • A. hasBoroughAcrossHudson
    Indicates that one entity has a borough or administrative subdivision located on the opposite side of the Hudson River from another referenced entity.
  • B. isHistoricHudsonRiverCommunity
    Indicates that a community is historically recognized as part of the Hudson River region, often due to its cultural, architectural, or historical significance tied to the river.
  • C. isRiverside
    Indicates that one entity is located beside or along the bank of a river in relation to another entity.
  • D. isRiversideRangeOf
    Indicates that something is a range or stretch of land that lies along the side of a river.
  • E. hasWatershed chosen
    Indicates that one geographic area or feature is part of, drains into, or is hydrologically defined by a particular watershed.
  • 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_69e2ff2b4c80819087c916b2b16241b9 completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f4549e7df48190aa0642008f748314 completed May 1, 2026, 7:22 a.m.
PD Predicate disambiguation batch_69f442c861188190967655c6d8012380 completed May 1, 2026, 6:06 a.m.
Created at: April 18, 2026, 6:08 a.m.