Triple
T5408170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OS Landranger 89 |
E120944
|
entity |
| Predicate | mapScaleCategory |
P63248
|
FINISHED |
| Object | small-scale topographic 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: small-scale topographic map | Statement: [OS Landranger 89, mapScaleCategory, small-scale topographic map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapScaleCategory Context triple: [OS Landranger 89, mapScaleCategory, small-scale topographic map]
-
A.
mapScale
Indicates the ratio between distances on a map and the corresponding actual distances in the real world.
-
B.
areaScale
Indicates a proportional relationship where one area value is a scaled (enlarged or reduced) version of another by a specific factor.
-
C.
distanceScaleRole
Indicates the role or function that a particular distance scale plays within a measurement, model, or spatial relationship.
-
D.
mapLabel
Indicates that a label or name is assigned to a map or mapped entity for identification or display.
-
E.
mapNumber
Indicates a correspondence where each element in one set or collection is assigned a specific numeric value in another set or domain.
- F. None of above. chosen
Provenance (4 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8794e0c4819082bebf2da5e41201 |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd865702ec8190831bde2c2a331f28 |
completed | March 20, 2026, 5:39 p.m. |
Created at: March 20, 2026, 2:05 p.m.