Triple
T720022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bass Rock |
E14394
|
entity |
| Predicate | approximateDistanceFromShore |
P15760
|
FINISHED |
| Object | about 5 kilometres from North Berwick |
—
|
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: about 5 kilometres from North Berwick | Statement: [Bass Rock, approximateDistanceFromShore, about 5 kilometres from North Berwick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDistanceFromShore Context triple: [Bass Rock, approximateDistanceFromShore, about 5 kilometres from North Berwick]
-
A.
distanceFromCoast
chosen
Indicates the measured spatial separation between a location and the nearest point on a coastline.
-
B.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
-
C.
distanceFromMainland
Indicates the measured spatial separation between a location and the nearest point on the mainland.
-
D.
positionRelativeToCoast
Indicates the spatial relationship of something to a coastline, such as its distance or orientation relative to the coast.
-
E.
distanceToPacificOcean
Indicates the physical distance between a given location or entity and the Pacific Ocean.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58e65e8819098cba7e6a20d8f33 |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f513608190b716b939d574c292 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.