Triple
T5014810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British National Grid |
E112713
|
entity |
| Predicate | gridReferenceFormat |
P53340
|
FINISHED |
| Object | alphanumeric grid reference |
—
|
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: alphanumeric grid reference | Statement: [British National Grid, gridReferenceFormat, alphanumeric grid reference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridReferenceFormat Context triple: [British National Grid, gridReferenceFormat, alphanumeric grid reference]
-
A.
gridReferenceType
Indicates the specific system or format used to express a location’s position within a spatial grid.
-
B.
hasOSGridReference
Indicates that an entity is associated with a specific Ordnance Survey grid reference location.
-
C.
coordinateFormat
chosen
Indicates the specific representation or notation used to express a set of coordinates.
-
D.
cartographicFormat
Indicates the specific cartographic representation or format in which spatial or map-related information is expressed.
-
E.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd732e0b848190858407920e7aefd0 |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.