Triple
T12772717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordnance Survey National Grid |
E305285
|
entity |
| Predicate | usesGridLetters |
P106824
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ordnance Survey National Grid, usesGridLetters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGridLetters Context triple: [Ordnance Survey National Grid, usesGridLetters, true]
-
A.
usesAdditionalLettersFrom
Indicates that one entity forms or derives its representation by incorporating extra letters taken from another entity beyond those originally present.
-
B.
isPartOfGrid
Indicates that something belongs to, is contained within, or forms a component of a larger grid structure.
-
C.
hasLetterDesignation
Indicates that an entity is assigned or associated with a specific letter-based designation or code.
-
D.
hasLettersFor
Indicates that one entity possesses or contains written correspondence intended for another entity.
-
E.
letterGroups
Indicates that entities are organized or associated into specific groups based on letters or letter-based criteria.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df5b68481908a5d40516b09be52 |
completed | April 10, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:28 p.m.