Triple
T35931937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentmere Horseshoe walk |
E1039186
|
entity |
| Predicate | includesFell |
—
|
GENERATED |
| Object | Yoke |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFell Context triple: [Kentmere Horseshoe walk, includesFell, Yoke]
-
A.
fellIn
Indicates that one entity moved downward, typically due to gravity or loss of support, and ended up inside or within the bounds of another entity or location.
-
B.
fallsIn
Indicates that one entity is located within, contained by, or geographically/administratively included inside another entity.
-
C.
hasNearbyFell
chosen
Indicates that one entity has a fell (a hill or high moorland area) located in close proximity to it.
-
D.
fellOn
Indicates that one entity moved downward, typically due to gravity, and came to rest on the surface of another entity.
-
E.
eventuallyFellAfter
Indicates that one event or state occurred at some point in time after another event or state, emphasizing that the later occurrence was not immediate but happened eventually.
- F. None of above.
Provenance (1 batch)
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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.