Triple
T34174946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbus Boulevard waterfront |
E876639
|
entity |
| Predicate | isShorelineType |
P71569
|
FINISHED |
| Object | urbanized 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: urbanized shoreline | Statement: [Columbus Boulevard waterfront, isShorelineType, urbanized shoreline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isShorelineType Context triple: [Columbus Boulevard waterfront, isShorelineType, urbanized shoreline]
-
A.
hasShorelineUse
Indicates that a geographic area or property is used for a particular type of activity or purpose along its shoreline.
-
B.
hasShorelineMaterial
Indicates that a geographic feature’s shoreline is composed of or characterized by a specified material.
-
C.
hasShorelineMarker
Indicates that a location or area is marked or delineated by a designated shoreline indicator or boundary marker.
-
D.
shorelineCharacteristic
chosen
Indicates the specific physical or environmental qualities that describe the nature or condition of a shoreline in relation to another entity.
-
E.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fe897048190971b6dc1f9e29f85 |
completed | May 3, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.