Triple
T14581386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willamette Falls |
E342199
|
entity |
| Predicate | navigationSolution |
P86898
|
FINISHED |
| Object | bypassed by Willamette Falls Locks |
—
|
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: bypassed by Willamette Falls Locks | Statement: [Willamette Falls, navigationSolution, bypassed by Willamette Falls Locks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationSolution Context triple: [Willamette Falls, navigationSolution, bypassed by Willamette Falls Locks]
-
A.
navigationProblemAddressed
chosen
Indicates that a navigation-related issue, obstacle, or challenge has been identified and dealt with or resolved.
-
B.
routePlan
Indicates a planned path or sequence of steps for traveling from a starting point to a destination.
-
C.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
D.
routeOptimization
Indicates the process of determining the most efficient path or sequence of paths between locations according to specified criteria such as distance, time, or cost.
-
E.
navigationImprovementFor
Indicates an action or change that enhances or optimizes the navigation capabilities or experience for a specified target.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb41e71748190a1deacc819dd26d3 |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.