Triple
T32913129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle metropolitan shoreline |
E841936
|
entity |
| Predicate | includesWaterfrontOf |
—
|
GENERATED |
| Object | City of Seattle |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesWaterfrontOf Context triple: [Seattle metropolitan shoreline, includesWaterfrontOf, City of Seattle]
-
A.
hasWaterfrontType
Indicates that an entity is associated with a specific type or category of waterfront (e.g., oceanfront, lakefront, riverfront).
-
B.
hasWaterfrontLocation
Indicates that an entity is situated directly adjacent to or along a body of water, such as a sea, lake, or river.
-
C.
hasWaterfrontAccessTo
Indicates that one entity is directly adjacent to and can physically access a particular body of water, such as a lake, river, or ocean.
-
D.
hasWaterfrontArea
chosen
Indicates that an entity possesses or includes an area directly adjacent to or bordering a body of water.
-
E.
isWaterfrontEstate
Indicates that a property is an estate located directly adjacent to a body of water, such as a lake, river, or ocean.
- F. None of above.
Provenance (1 batch)
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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:19 a.m.