Triple
T23496364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Screes |
E571713
|
entity |
| Predicate | hasTypicalAccessPoint |
P81316
|
FINISHED |
| Object | Kirkstone Pass car park |
—
|
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: Kirkstone Pass car park | Statement: [Red Screes, hasTypicalAccessPoint, Kirkstone Pass car park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalAccessPoint Context triple: [Red Screes, hasTypicalAccessPoint, Kirkstone Pass car park]
-
A.
hasTypicalAccess
Indicates that one entity normally or customarily has the ability, permission, or means to access or use another entity.
-
B.
hasAccessPointFrom
chosen
Indicates that an entity can be reached or entered from a specific access point.
-
C.
hasModernAccessPoint
Indicates that one entity provides or includes a contemporary means or facility through which another entity can be accessed or used.
-
D.
typeOfAccessPoint
Indicates the specific kind or category of access point involved in the relationship or action.
-
E.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7e00384819092729319a378d4ab |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:05 p.m.