Triple
T987703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitestone Bridge |
E21314
|
entity |
| Predicate | riverMouthProximity |
P8567
|
FINISHED |
| Object | near East River–Long Island Sound junction |
—
|
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 East River–Long Island Sound junction | Statement: [Whitestone Bridge, riverMouthProximity, near East River–Long Island Sound junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverMouthProximity Context triple: [Whitestone Bridge, riverMouthProximity, near East River–Long Island Sound junction]
-
A.
nearbyWatercourse
chosen
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
-
B.
mouthOfWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water or another watercourse.
-
C.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
-
D.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
-
E.
distanceFromCoast
Indicates the measured spatial separation between a location and the nearest point on a coastline.
- 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4a89a58819081a24b5b0a12f122 |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2abccbc8190a83af432f89eacf5 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.