Triple
T1224704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park Avenue Bridge |
E26299
|
entity |
| Predicate | crossesAtMilepost |
P26022
|
FINISHED |
| Object | near Harlem River mouth |
—
|
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: near Harlem River mouth | Statement: [Park Avenue Bridge, crossesAtMilepost, near Harlem River mouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesAtMilepost Context triple: [Park Avenue Bridge, crossesAtMilepost, near Harlem River mouth]
-
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.
crossesSectionOf
Indicates that one entity passes through or over a specific segment or portion of another entity.
-
C.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
D.
hadCrossingPoints
Indicates that two entities intersected or overlapped at one or more specific points in space or time.
-
E.
oftenCrossedOn
Indicates that one entity is frequently traversed or passed over by another entity.
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be382c4081909238c18b805352a7 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bd3140688190ac6e24de157fd61e |
completed | March 1, 2026, 10:26 p.m. |
Created at: March 1, 2026, 7:47 p.m.