Triple
T32892701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Fordham Road |
E841379
|
entity |
| Predicate | crossesBoroughFeature |
P183532
|
FINISHED |
| Object | Harlem River Ship Canal |
—
|
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: Harlem River Ship Canal | Statement: [West Fordham Road, crossesBoroughFeature, Harlem River Ship Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesBoroughFeature Context triple: [West Fordham Road, crossesBoroughFeature, Harlem River Ship Canal]
-
A.
crossesBetween
Indicates that one entity passes from one side of a second entity to the other, traversing the space between two reference points or boundaries associated with that second entity.
-
B.
crossesInCityArea
Indicates that one entity crosses or passes through another entity specifically within an urban or city-designated area.
-
C.
crossesInCity
Indicates that one entity crosses or passes through another entity within the boundaries of a specified city.
-
D.
hasCrossStreets
Indicates that a location is situated at or near the intersection of the specified streets.
-
E.
connectsBoroughsOf
Indicates a relationship where something serves as a link or route joining two or more boroughs to each other.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: May 1, 2026, 1:18 a.m.