Triple
T18432694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Pablo Peninsula |
E450310
|
entity |
| Predicate | hasBayShoreOrientation |
P91974
|
FINISHED |
| Object | west-facing shoreline |
—
|
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: west-facing shoreline | Statement: [San Pablo Peninsula, hasBayShoreOrientation, west-facing shoreline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBayShoreOrientation Context triple: [San Pablo Peninsula, hasBayShoreOrientation, west-facing shoreline]
-
A.
hasShoreOrientation
chosen
Indicates the directional orientation of a shoreline relative to a reference frame (e.g., compass direction or facing).
-
B.
hasBayShape
Indicates that an entity possesses or exhibits a particular geometric or physical shape characteristic of a bay.
-
C.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
D.
oceanOrientation
Indicates the directional alignment or facing of something relative to an ocean.
-
E.
hasLakeshore
Indicates that one entity is located along or directly borders the shore of a lake associated with another entity.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b183adc8190987bc7749d0e673c |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:27 a.m.