Triple
T30159309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ME postcode area |
E766612
|
entity |
| Predicate | hasSortingInfrastructure |
P181332
|
FINISHED |
| Object | Royal Mail sorting offices in the region |
—
|
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: Royal Mail sorting offices in the region | Statement: [ME postcode area, hasSortingInfrastructure, Royal Mail sorting offices in the region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSortingInfrastructure Context triple: [ME postcode area, hasSortingInfrastructure, Royal Mail sorting offices in the region]
-
A.
hasSort
Indicates that one entity is associated with, or classified by, a particular sort, type, or category.
-
B.
supportsOnlineSorting
Indicates that the subject provides functionality for arranging items or data in different orders through an online or digital interface.
-
C.
sortingOrderSupport
Indicates whether a system or component supports arranging items according to a specified sorting order.
-
D.
hasOrderingMethod
Indicates that there is a specific method or procedure used to place or arrange an order for something.
-
E.
isComparisonSort
Indicates that the sorting algorithm operates by comparing pairs of elements to determine their order.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
| PDg | Predicate description generation | batch_69f7688cea58819098bdfd7c80df7634 |
completed | May 3, 2026, 3:23 p.m. |
Created at: April 29, 2026, 7:21 p.m.