Triple
T1127831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 145th Street Bridge |
E24759
|
entity |
| Predicate | riverBankOnOneSide |
P25281
|
FINISHED |
| Object | Manhattan bank of Harlem 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: Manhattan bank of Harlem River | Statement: [145th Street Bridge, riverBankOnOneSide, Manhattan bank of Harlem River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverBankOnOneSide Context triple: [145th Street Bridge, riverBankOnOneSide, Manhattan bank of Harlem River]
-
A.
locatedAcrossRiverFrom
Indicates that one entity is situated on the opposite side of a river relative to another entity.
-
B.
hasParkAlongBank
Indicates that a park is located adjacent to or running alongside the bank of a water body.
-
C.
majorPortOnRiver
Indicates that a port is a primary or significant harbor facility located on the banks of a specified river.
-
D.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
E.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
- 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_69a4940712c88190aa244f3fc6070a65 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb48de2081909a0dce005b1c9df1 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bc47fce48190825d3a877251f789 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:44 p.m.