Triple
T32087605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 92 |
E819490
|
entity |
| Predicate | bayCrossing |
P103014
|
FINISHED |
| Object | San Mateo–Hayward 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: San Mateo–Hayward Bridge | Statement: [SR 92, bayCrossing, San Mateo–Hayward Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bayCrossing Context triple: [SR 92, bayCrossing, San Mateo–Hayward Bridge]
-
A.
hasBayCrossing
chosen
Indicates that one place is connected to another by a crossing over a bay, such as a bridge, tunnel, or ferry route.
-
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.
waterwayTypeCrossed
Indicates the specific kind of waterway (e.g., river, canal, stream) that is being crossed in the described relationship or action.
-
D.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
E.
wasMainRiverCrossingFor
Indicates that one river crossing (such as a bridge, ford, or ferry) served as the primary or most significant crossing point for a particular route, area, or settlement.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:25 a.m.