Triple
T35835146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware and Hudson Railway |
E1035911
|
entity |
| Predicate | connectedToRiver |
P180780
|
FINISHED |
| Object | Delaware River |
—
|
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: Delaware River | Statement: [Delaware and Hudson Railway, connectedToRiver, Delaware River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToRiver Context triple: [Delaware and Hudson Railway, connectedToRiver, Delaware River]
-
A.
linkedToRiver
chosen
Indicates a relationship where something is physically or functionally connected to, associated with, or dependent on a river.
-
B.
locatedInRiverArea
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
-
C.
locatedBetweenRiver
Indicates that an entity is situated in the area or region between two segments or banks of a river, or between two rivers.
-
D.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
E.
reachedRiver
Indicates that an entity has arrived at or come into contact with a river as a result of movement or travel.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:06 p.m.