Triple
T27458409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York Way |
E692663
|
entity |
| Predicate | hasPostcodeAreasAlong |
P186447
|
FINISHED |
| Object | N1 |
—
|
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: N1 | Statement: [York Way, hasPostcodeAreasAlong, N1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostcodeAreasAlong Context triple: [York Way, hasPostcodeAreasAlong, N1]
-
A.
hasPostcodeSector
Indicates that an entity is associated with a specific postcode sector within a postal addressing system.
-
B.
hasPostcodeDistrictsApprox
Indicates that one entity is associated with a set of postcode districts in an approximate or non-exact manner.
-
C.
hasPostcodeDistrictCode
Indicates that an entity is associated with a specific postcode district code within a postal addressing system.
-
D.
hasNeighbouringPostcodeDistrict
Indicates that one postcode district is geographically adjacent to or directly borders another postcode district.
-
E.
postcodeAreaCountApprox
Indicates an approximate count of postcode areas associated with an entity.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: April 27, 2026, 12:49 p.m.