Triple
T25270645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OS Landranger 110 |
E633557
|
entity |
| Predicate | cartographicContent |
P158079
|
FINISHED |
| Object | transport network |
—
|
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: transport network | Statement: [OS Landranger 110, cartographicContent, transport network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cartographicContent Context triple: [OS Landranger 110, cartographicContent, transport network]
-
A.
cartographicContent
chosen
Indicates that the resource contains or is associated with map-related or cartographic information.
-
B.
cartographicWork
Indicates a relationship where one entity is a cartographic work (such as a map or chart) that represents geographic information about another entity.
-
C.
cartographicContext
Indicates the mapping or geographic framework within which something is spatially represented or interpreted.
-
D.
cartographicNotation
Indicates the specific symbols, labels, or graphical conventions used to represent geographic features or spatial information on a map.
-
E.
cartographicUse
Indicates the way in which something is used or intended to be used within a cartographic or map-making context.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48ba1a1f88190b3db79ec06bfa994 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:16 p.m.