Triple
T24501513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OS Landranger 90 |
E617943
|
entity |
| Predicate | mapSymbolSystem |
P117751
|
FINISHED |
| Object | Ordnance Survey cartographic symbols |
—
|
NE NERFINISHED |
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: Ordnance Survey cartographic symbols | Statement: [OS Landranger 90, mapSymbolSystem, Ordnance Survey cartographic symbols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapSymbolSystem Context triple: [OS Landranger 90, mapSymbolSystem, Ordnance Survey cartographic symbols]
-
A.
mapSymbol
Indicates a correspondence where one symbol is used to represent, stand for, or denote another element within a mapping or representation system.
-
B.
mapSymbolStandard
chosen
Indicates that a map symbol conforms to, or is defined according to, a particular cartographic standard or specification.
-
C.
mapSystem
Indicates a relationship where one system is associated with or represented by a specific map or mapping framework.
-
D.
pointsSymbolize
Indicates that specific points are used to represent or stand for particular meanings, concepts, or values.
-
E.
cartographicNotation
Indicates the specific symbols, labels, or graphical conventions used to represent geographic features or spatial information on a map.
- 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_69e2d7f682108190a1a7ca5fd485ee8a |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:23 a.m.