Triple
T5173906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swinbrook |
E116748
|
entity |
| Predicate | postCodeDistrict |
P222
|
FINISHED |
| Object | OX18 |
—
|
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: OX18 | Statement: [Swinbrook, postCodeDistrict, OX18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postCodeDistrict Context triple: [Swinbrook, postCodeDistrict, OX18]
-
A.
postalArea
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
-
B.
hasPostcodeDistrictsApprox
Indicates that one entity is associated with a set of postcode districts in an approximate or non-exact manner.
-
C.
targetCityDistrict
Indicates that one entity is a specific city district that serves as the target or destination in relation to another entity.
-
D.
districtCode
Indicates that an entity is associated with, or identified by, a specific administrative district code.
-
E.
postalCode
chosen
Indicates the numerical or alphanumerical code assigned to a geographic area for mail delivery associated with an entity.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd796f7c308190a721e33aabd499ac |
completed | March 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69bd77b529948190b86671ebe43f4734 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.