Triple
T26072025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grisedale valley |
E657575
|
entity |
| Predicate | hasHeadOfValleyNear |
P168554
|
FINISHED |
| Object | Grisedale Tarn |
—
|
NE NERFINISHED |
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: Grisedale Tarn | Statement: [Grisedale valley, hasHeadOfValleyNear, Grisedale Tarn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadOfValleyNear Context triple: [Grisedale valley, hasHeadOfValleyNear, Grisedale Tarn]
-
A.
hasHighestPointNear
Indicates that one entity’s highest point is located close to another specified entity or location.
-
B.
hasValley
Indicates that one entity contains, features, or is characterized by the presence of a valley associated with the other entity.
-
C.
hasNearestMountain
Indicates that one entity is the closest mountain geographically relative to another entity.
-
D.
valleyLocation
Indicates that one entity is located in, at, or within the geographic bounds of a valley relative to another entity or context.
-
E.
hasMountainPassNearby
Indicates that a mountain pass is located in close proximity to the referenced place or feature.
- F. None of above. chosen
Provenance (4 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 26, 2026, 7:30 p.m.