Triple
T2248779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Highway |
E49566
|
entity |
| Predicate | coastalRouteAlong |
P32976
|
FINISHED |
| Object | Pacific coastline of San Francisco |
—
|
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: Pacific coastline of San Francisco | Statement: [Great Highway, coastalRouteAlong, Pacific coastline of San Francisco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalRouteAlong Context triple: [Great Highway, coastalRouteAlong, Pacific coastline of San Francisco]
-
A.
extendsAlongCoastOf
Indicates that one entity stretches or runs parallel along the coastline of another entity.
-
B.
flowsAlongCoastOf
Indicates that something, typically a body of water or current, moves in a path that follows and runs adjacent to a coastline.
-
C.
hasCoastalPath
chosen
Indicates that there exists a designated path or route running along or adjacent to the coastline of a given area or feature.
-
D.
coastlineFeature
Indicates that a geographic entity is a specific type of feature located along or forming part of a coastline.
-
E.
coastOff
Indicates that one entity is located just off the coast of another, typically in nearby offshore waters rather than directly on the shoreline.
- 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_69a88aa979788190ad6500f1d8eee2fc |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0ef74988190a0af51d983cf5658 |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.