Triple
T20963513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blea Moor Tunnel |
E516308
|
entity |
| Predicate | southPortalLocation |
P15806
|
FINISHED |
| Object | near Ribblehead |
—
|
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: near Ribblehead | Statement: [Blea Moor Tunnel, southPortalLocation, near Ribblehead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: southPortalLocation Context triple: [Blea Moor Tunnel, southPortalLocation, near Ribblehead]
-
A.
southernGate
Indicates that one entity serves as or is located at the southern gate or southern entrance relative to another entity.
-
B.
elevationSouthPortal
Indicates the vertical height or altitude measured at the southern portal of a structure or feature.
-
C.
portalLocation
chosen
Indicates that a portal is situated at or associated with a specific location.
-
D.
terminusSouthNear
Indicates that the southern end or terminus of one entity is located close to another entity.
-
E.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb710d6c8190a2daacaad3b22683 |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:32 p.m.