Triple
T24246963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troy–Menands Bridge area near Troy, New York |
E603402
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | river crossing area |
C12216
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: river crossing area Context triple: [Troy–Menands Bridge area near Troy, New York, instanceOf, river crossing area]
-
A.
river crossing
chosen
A river crossing is a location or method by which people, animals, or vehicles traverse from one side of a river to the other, using natural shallows, bridges, ferries, or other means.
-
B.
river border area
A river border area is a geographic zone where a river serves as a natural boundary between adjacent political or administrative regions, encompassing the waterway and its immediate banks.
-
C.
river crossing operation
A river crossing operation is a coordinated military or logistical maneuver to move personnel, vehicles, and equipment across a water obstacle using specialized planning, equipment, and tactics while mitigating environmental and enemy threats.
-
D.
river corridor
A river corridor is the linear landscape surrounding a river, including its channel, banks, floodplain, and adjacent habitats, through which water, sediment, organisms, and energy flow and interact.
-
E.
river bar
A river bar is an elongated accumulation of sediment, such as sand or gravel, deposited within or along a river channel by flowing water.
- F. None of above.
Provenance (1 batch)
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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:04 a.m.