Triple
T30221316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 14 |
E768350
|
entity |
| Predicate | connectsToBridge |
P36619
|
FINISHED |
| Object | Hood River Bridge |
—
|
NE NERFINISHED |
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: Hood River Bridge | Statement: [SR 14, connectsToBridge, Hood River Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToBridge Context triple: [SR 14, connectsToBridge, Hood River Bridge]
-
A.
hasBridgeTo
chosen
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
B.
supportsBridging
Indicates that one entity enables or facilitates a bridging connection or transition between two otherwise separate entities, systems, or contexts.
-
C.
hasBridgeAccess
Indicates that an entity is permitted to enter or use a specific bridge or bridge-controlled area.
-
D.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
E.
hasNearbyBridge
Indicates that one entity is located close to a bridge associated with or relevant to it.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: April 29, 2026, 7:35 p.m.