Triple
T3802833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester Outer Ring Road |
E91729
|
entity |
| Predicate | roadHierarchyLevel |
P19386
|
FINISHED |
| Object | major route |
—
|
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: major route | Statement: [Manchester Outer Ring Road, roadHierarchyLevel, major route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadHierarchyLevel Context triple: [Manchester Outer Ring Road, roadHierarchyLevel, major route]
-
A.
hasStreetLevel
Indicates that something is located at, accessible from, or directly associated with the street level of a building or area.
-
B.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
C.
roadImportance
chosen
Indicates the relative significance or priority of a road within a transportation network, such as its role in connectivity, traffic flow, or access.
-
D.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
E.
railroadHierarchyLevel
Indicates the position or rank of a railroad-related entity within an ordered organizational or structural hierarchy.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.