Triple
T31137998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastshore State Park |
E793698
|
entity |
| Predicate | followsShorelineBetween |
P1865
|
FINISHED |
| Object | Emeryville |
—
|
NE NERFINISHED |
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: Emeryville | Statement: [Eastshore State Park, followsShorelineBetween, Emeryville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsShorelineBetween Context triple: [Eastshore State Park, followsShorelineBetween, Emeryville]
-
A.
followsCoast
chosen
Indicates that one entity’s path or boundary runs alongside and generally conforms to the shape of a coastline.
-
B.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
-
C.
formsShorelineOf
Indicates that one geographic feature constitutes or defines the boundary or edge (shoreline) of a body of water.
-
D.
formsPartOfShorelineNear
Indicates that one entity constitutes a segment of the shoreline located in the vicinity of another entity.
-
E.
hasShorelineTrail
Indicates that a location or body of water is connected to or bordered by a trail that runs along its 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: April 29, 2026, 9:05 p.m.