Triple
T32336558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point Molate Naval Fuel Depot |
E826189
|
entity |
| Predicate | locatedOnShorelineOf |
P84004
|
FINISHED |
| Object | San Pablo Bay |
E19744
|
NE 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 Pablo Bay | Statement: [Point Molate Naval Fuel Depot, locatedOnShorelineOf, San Pablo Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnShorelineOf Context triple: [Point Molate Naval Fuel Depot, locatedOnShorelineOf, San Pablo Bay]
-
A.
locatedOnCoastAt
chosen
Indicates that one entity is situated on the coastline at the specific location represented by another entity.
-
B.
locatedOnWesternShoreOf
Indicates that one entity is situated along the western shore or coastline of another entity.
-
C.
locatedOnEasternShoreOf
Indicates that one entity is situated on the eastern shore or bank of another geographic feature, such as a body of water or landform.
-
D.
hasCityOnShore
Indicates that a city is located on or directly adjacent to the shore of a body of water.
-
E.
connectsToCoastAt
Indicates that one entity has a direct physical or geographical connection or access to a coastline at the location of another entity.
- F. None of above.
Provenance (4 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a02f2d6f35481909829d4ec710dcb0f |
completed | May 12, 2026, 9:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a33e89b9a4c8190a65e3ac7e74296f7 |
completed | June 18, 2026, 12:46 p.m. |
| PD | Predicate disambiguation | batch_6a02f15a2460819080cb4be5b50221d0 |
completed | May 12, 2026, 9:22 a.m. |
Created at: May 1, 2026, 12:48 a.m.