Triple
T17403125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogue River Bridge |
E423144
|
entity |
| Predicate | crossesAtMouthOf |
P27425
|
FINISHED |
| Object | Rogue River near Pacific Ocean |
—
|
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: Rogue River near Pacific Ocean | Statement: [Rogue River Bridge, crossesAtMouthOf, Rogue River near Pacific Ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesAtMouthOf Context triple: [Rogue River Bridge, crossesAtMouthOf, Rogue River near Pacific Ocean]
-
A.
mouthOf
Indicates the location where one entity (typically a river or similar feature) empties into or opens out into another, larger body or feature.
-
B.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
C.
containsMouthOf
Indicates that one entity geographically includes or encompasses the mouth (outflow point) of another entity, such as a river or stream.
-
D.
crossesIn
chosen
Indicates that one entity passes over or through the path, boundary, or area occupied by another entity, intersecting its space or trajectory.
-
E.
crossesNear
Indicates that one entity passes across the path or area of another entity at a location that is close to, but not directly intersecting, the other entity.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43b051cc48190872278ee0b52240d |
completed | April 19, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.