Triple
T10987236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fremont Cut |
E259661
|
entity |
| Predicate | hasBridgeTypeOver |
P30343
|
FINISHED |
| Object | bascule bridge (Fremont Bridge) |
—
|
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: bascule bridge (Fremont Bridge) | Statement: [Fremont Cut, hasBridgeTypeOver, bascule bridge (Fremont Bridge)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBridgeTypeOver Context triple: [Fremont Cut, hasBridgeTypeOver, bascule bridge (Fremont Bridge)]
-
A.
hasBridgeTypeCrossing
chosen
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
-
B.
hasBridgeTunnel
Indicates that there exists a bridge or tunnel connection between two locations or structures.
-
C.
hasBridgeOrStructure
Indicates that there exists a bridge or similar structural connection between the related entities.
-
D.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
E.
hasBridgeUnderpasses
Indicates that one structure, typically a bridge, includes or provides underpasses that allow passage beneath 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d787b3c8388190be77e95d56979a7f |
completed | April 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.