Triple
T24026184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peak District road network |
E594964
|
entity |
| Predicate | hasMinorRoad |
P134934
|
FINISHED |
| Object | B roads in the Peak District |
—
|
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: B roads in the Peak District | Statement: [Peak District road network, hasMinorRoad, B roads in the Peak District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMinorRoad Context triple: [Peak District road network, hasMinorRoad, B roads in the Peak District]
-
A.
isMinorRoadIn
chosen
Indicates that a minor (smaller or less significant) road is located within or forms part of a specified larger area, route, or network.
-
B.
isMainRoad
Indicates that a road serves as a primary or major thoroughfare within a transportation network.
-
C.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
D.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
E.
isOnlyMajorRoadAccessTo
Indicates that one road is the sole major roadway providing access to a particular place or area.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d76ada608190a9b63d07c2fa90d4 |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:53 p.m.