Triple
T25520749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamlet of Hudson, New York |
E639639
|
entity |
| Predicate | isInHudsonValley |
P56914
|
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: [Hamlet of Hudson, New York, isInHudsonValley, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInHudsonValley Context triple: [Hamlet of Hudson, New York, isInHudsonValley, 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.
isInUpstateNewYork
Indicates that a location or entity is situated within the geographic region commonly referred to as Upstate New York.
-
D.
isInUnionCounty
Indicates that one entity is located within, or falls under the jurisdiction of, Union County.
-
E.
isInValley
chosen
Indicates that an entity is located within or occupies the area of a valley.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f836387c8190813f5c202ff47a8c |
completed | May 2, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3 p.m.