Triple
T6165292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Shore Road, Bermuda |
E137541
|
entity |
| Predicate | runsAlongShoreline |
P18703
|
FINISHED |
| Object | northern shoreline of Bermuda |
—
|
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: northern shoreline of Bermuda | Statement: [North Shore Road, Bermuda, runsAlongShoreline, northern shoreline of Bermuda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsAlongShoreline Context triple: [North Shore Road, Bermuda, runsAlongShoreline, northern shoreline of Bermuda]
-
A.
extendsAlongCoastOf
chosen
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.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
-
D.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
-
E.
hasHighwayAlongShore
Indicates that a highway runs adjacent to or closely follows the shoreline of a body of water.
- 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_69c008a54fc88190b6ce4416490ca79d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d6225bc819097707be620681e7b |
completed | March 22, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:17 p.m.