Triple
T23221691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson River Railroad |
E580910
|
entity |
| Predicate | routeAlong |
P151412
|
FINISHED |
| Object | east bank of the Hudson River |
—
|
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: east bank of the Hudson River | Statement: [Hudson River Railroad, routeAlong, east bank of the Hudson River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeAlong Context triple: [Hudson River Railroad, routeAlong, east bank of the Hudson River]
-
A.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
B.
routePlan
Indicates a planned path or sequence of steps for traveling from a starting point to a destination.
-
C.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
-
D.
routeDirectionB
Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
-
E.
routeDirectionA
Indicates the primary or first directional orientation or heading associated with a specific route.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1922924308190a26b00e09ce60ecd |
completed | April 29, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:08 p.m.