Triple
T21836868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cladach |
E539141
|
entity |
| Predicate | hasTrailheadRole |
P123917
|
FINISHED |
| Object | starting point for Goat Fell ascent |
—
|
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: starting point for Goat Fell ascent | Statement: [Cladach, hasTrailheadRole, starting point for Goat Fell ascent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrailheadRole Context triple: [Cladach, hasTrailheadRole, starting point for Goat Fell ascent]
-
A.
hasTrailheadAt
Indicates that a trail or route begins or has its official starting point at a specified location.
-
B.
hasOfficialTrailhead
Indicates that a location or route is associated with a formally designated and recognized starting point for a trail.
-
C.
hasTrailheadArea
chosen
Indicates that a location serves as the starting area or access point for a trail or network of trails.
-
D.
hasTrailheadBelow
Indicates that the starting point of a trail is located at a lower elevation or position relative to another referenced feature or location.
-
E.
accessTrailhead
Indicates that an entity has a way to reach or enter a specific trailhead location.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7a890208190a902184e60194e1c |
completed | April 28, 2026, 12:27 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.