Triple
T22084599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordnance Survey Landranger maps |
E545739
|
entity |
| Predicate | mapSheetFormat |
P58709
|
FINISHED |
| Object | paper map |
—
|
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: paper map | Statement: [Ordnance Survey Landranger maps, mapSheetFormat, paper map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapSheetFormat Context triple: [Ordnance Survey Landranger maps, mapSheetFormat, paper map]
-
A.
cartographicFormat
chosen
Indicates the specific cartographic representation or format in which spatial or map-related information is expressed.
-
B.
cartographicType
Indicates the specific kind or category of cartographic representation associated with an entity (e.g., map type or mapping style).
-
C.
mapNumber
Indicates a correspondence where each element in one set or collection is assigned a specific numeric value in another set or domain.
-
D.
cartographicNotation
Indicates the specific symbols, labels, or graphical conventions used to represent geographic features or spatial information on a map.
-
E.
fileFormatStandard
Indicates that something conforms to, specifies, or defines a standardized structure and rules for how data is organized and stored in a file.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b95e908190bd846f531eb59b50 |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.