Triple
T24779369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardknott Pass |
E619948
|
entity |
| Predicate | formsRouteWith |
P5619
|
FINISHED |
| Object | Wrynose Pass |
—
|
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: Wrynose Pass | Statement: [Hardknott Pass, formsRouteWith, Wrynose Pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsRouteWith Context triple: [Hardknott Pass, formsRouteWith, Wrynose Pass]
-
A.
formsKeyRouteTo
Indicates that something serves as a primary or essential pathway or connection leading to another thing.
-
B.
formsWith
Indicates that one entity combines or associates with another to create or constitute a joint structure, group, or configuration.
-
C.
exportRoute
Indicates the route or pathway through which goods, services, or data are exported from one location or entity to another.
-
D.
formsFacadeOf
Indicates that one entity serves as the outward-facing surface or front (facade) of another entity, typically concealing or enclosing it.
-
E.
route
chosen
Indicates that one entity serves as a path or course used to travel or move between locations 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:43 a.m.