Triple
T21330350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buttermere |
E525880
|
entity |
| Predicate | hasShorePath |
P32976
|
FINISHED |
| Object | circular path around lake |
—
|
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: circular path around lake | Statement: [Buttermere, hasShorePath, circular path around lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShorePath Context triple: [Buttermere, hasShorePath, circular path around lake]
-
A.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
B.
hasShoreFeature
Indicates that a shore or coastline possesses a specific physical or environmental feature.
-
C.
hasShoreOrientation
Indicates the directional orientation of a shoreline relative to a reference frame (e.g., compass direction or facing).
-
D.
hasCoastalPath
chosen
Indicates that there exists a designated path or route running along or adjacent to the coastline of a given area or feature.
-
E.
hasShorelineMarker
Indicates that a location or area is marked or delineated by a designated shoreline indicator or boundary marker.
- 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_69e0b51b90788190a4dd823d962626da |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7ab5177dc8190b888351e9a45b45f |
completed | April 21, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:42 p.m.