Triple
T2603754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Highways |
E58605
|
entity |
| Predicate | managesNetworkType |
P5033
|
FINISHED |
| Object | strategic road network in England |
—
|
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: strategic road network in England | Statement: [National Highways, managesNetworkType, strategic road network in England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesNetworkType Context triple: [National Highways, managesNetworkType, strategic road network in England]
-
A.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
B.
routeNetworkType
Indicates the specific kind of transportation or communication network to which a route belongs (e.g., road, rail, or air).
-
C.
operatesNetwork
chosen
Indicates that an entity manages, controls, or runs the functioning of a network.
-
D.
supportsNetworkingModel
Indicates that one entity provides compatibility with, or implementation of, a specified networking model for another entity.
-
E.
typeOfEquipmentManaged
Indicates the specific kind or category of equipment that an entity is responsible for managing.
- 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8def9bc8190b2e013abffc7b191 |
completed | March 7, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_69abd80ab7248190ba06ba14fe4c5638 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:49 p.m.