Triple
T38603594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OS Explorer 265 (Clwydian Range) |
E934282
|
entity |
| Predicate | usesGridSystem |
P191283
|
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 265 (Clwydian Range), usesGridSystem, British National Grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGridSystem Context triple: [OS Explorer 265 (Clwydian Range), usesGridSystem, British National Grid]
-
A.
usesGridBasedLayout
Indicates that an entity arranges its elements or content according to a structured grid-based layout system.
-
B.
isPartOfGrid
Indicates that something belongs to, is contained within, or forms a component of a larger grid structure.
-
C.
usesGridLetters
Indicates that one entity employs or incorporates the letters or coordinates of a grid in relation to another entity or context.
-
D.
regulatesGridThrough
Indicates that one entity controls or influences the operation or behavior of an electrical grid by means of another specified intermediary or mechanism.
-
E.
gridType
Indicates the specific structural or organizational pattern of a grid used to arrange or reference elements.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdb0cf6008190b27046b694f84356 |
completed | May 7, 2026, 6:33 p.m. |
Created at: May 3, 2026, 4:32 p.m.