Triple
T27648919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OS Explorer OL5 |
E696791
|
entity |
| Predicate | usesGrid |
P106824
|
FINISHED |
| Object | British National Grid |
—
|
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: British National Grid | Statement: [OS Explorer OL5, usesGrid, British National Grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGrid Context triple: [OS Explorer OL5, usesGrid, British National Grid]
-
A.
isPartOfGrid
Indicates that something belongs to, is contained within, or forms a component of a larger grid structure.
-
B.
usesGridBasedLayout
Indicates that an entity arranges its elements or content according to a structured grid-based layout system.
-
C.
usesGridLetters
chosen
Indicates that one entity employs or incorporates the letters or coordinates of a grid in relation to another entity or context.
-
D.
usesFrame
Indicates that one entity employs, relies on, or is structured around a particular frame, framework, or reference structure provided by another entity.
-
E.
regulatesGridThrough
Indicates that one entity controls or influences the operation or behavior of an electrical grid by means of another specified intermediary or mechanism.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:31 p.m.