Triple
T33165787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Route 23B |
E848880
|
entity |
| Predicate | providesLocalAccessTo |
P51771
|
FINISHED |
| Object | Hudson, 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, New York | Statement: [New York State Route 23B, providesLocalAccessTo, Hudson, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesLocalAccessTo Context triple: [New York State Route 23B, providesLocalAccessTo, Hudson, New York]
-
A.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
-
B.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
-
C.
accessProvides
chosen
Indicates that one entity grants or enables the ability to use, enter, or retrieve another entity or resource.
-
D.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
E.
hasNearbyPortAccess
Indicates that an entity is located close enough to a port to feasibly use it for access or transport.
- 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: May 1, 2026, 1:28 a.m.