Triple
T24959657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandy Hill, New York |
E624571
|
entity |
| Predicate | isVillageNameOf |
P157275
|
FINISHED |
| Object | Hudson Falls, New York |
—
|
NE NERFINISHED |
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: Hudson Falls, New York | Statement: [Sandy Hill, New York, isVillageNameOf, Hudson Falls, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVillageNameOf Context triple: [Sandy Hill, New York, isVillageNameOf, Hudson Falls, New York]
-
A.
isVillage
Indicates that the subject entity is classified as a village, typically a small human settlement or community.
-
B.
isInVillage
Indicates that one entity is located within or belongs to the area defined as a village in relation to another entity.
-
C.
isAncestralVillageOf
Indicates that one place is the original home or traditional village from which another person, family, or community traces its ancestry.
-
D.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
E.
canAppearWithVillageNameOnLabel
Indicates that an entity is permitted to be displayed together with a village name on a product label.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4242c447c8190bf7972390ac93814 |
completed | May 1, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f423637bec8190a1701421ac86a3b7 |
completed | May 1, 2026, 3:52 a.m. |
Created at: April 18, 2026, 5:58 a.m.