Triple
T603013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Gate Bridge |
E11534
|
entity |
| Predicate | crossesBodyOfWater |
P15424
|
FINISHED |
| Object | San Francisco Bay entrance |
—
|
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: San Francisco Bay entrance | Statement: [Golden Gate Bridge, crossesBodyOfWater, San Francisco Bay entrance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesBodyOfWater Context triple: [Golden Gate Bridge, crossesBodyOfWater, San Francisco Bay entrance]
-
A.
crossesWaterBody
chosen
Indicates that an entity moves from one side of a water body to the other by passing over, through, or across it.
-
B.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
C.
locatedInBodyOfWater
Indicates that an entity is situated within or on the surface of a specific body of water.
-
D.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
E.
appliesToWaterBody
Indicates that something (such as a rule, condition, property, or effect) is relevant or applicable specifically to a particular 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e574444819087999404f3e3ffd9 |
completed | March 1, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69a49cf701e08190966d06b9ff4b582b |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.