Triple
T20481607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woz Way Bridge (San Jose) |
E502467
|
entity |
| Predicate | hasRiverBankContext |
P8340
|
FINISHED |
| Object | Guadalupe River floodplain |
—
|
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: Guadalupe River floodplain | Statement: [Woz Way Bridge (San Jose), hasRiverBankContext, Guadalupe River floodplain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverBankContext Context triple: [Woz Way Bridge (San Jose), hasRiverBankContext, Guadalupe River floodplain]
-
A.
hasRiverBankSettlement
Indicates that a settlement is located on or directly adjacent to the bank of a river.
-
B.
borderRiverContext
Indicates that a river serves as or is involved in forming the boundary between two geographic or political regions within a specific contextual setting.
-
C.
hasLandmarkOnBank
chosen
Indicates that a landmark is located on the bank (shore or edge) of a geographic feature such as a river, lake, or canal.
-
D.
hasRiverCode
Indicates that a river is associated with a specific identifying code or classification value.
-
E.
hasParkAlongBank
Indicates that a park is located adjacent to or running alongside the bank of a water body.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b57fa9c819091d12320d46a0cee |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:34 a.m.