Triple
T35812613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HA postcode area |
E1035271
|
entity |
| Predicate | containsPostalDistrict |
P32592
|
FINISHED |
| Object | HA0 |
—
|
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: HA0 | Statement: [HA postcode area, containsPostalDistrict, HA0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPostalDistrict Context triple: [HA postcode area, containsPostalDistrict, HA0]
-
A.
hasPostcodeDistrictCode
Indicates that an entity is associated with a specific postcode district code within a postal addressing system.
-
B.
hasPostcodeDistrictNumber
Indicates that an entity is associated with a specific numerical postcode district identifier within a postal code system.
-
C.
isCentralPostalDistrict
Indicates that a given postal district serves as the primary or central postal area within a city or region.
-
D.
postalAreaIncludes
chosen
Indicates that a given postal area geographically contains or covers another specified location or region.
-
E.
hasPostcodeDistrictsApprox
Indicates that one entity is associated with a set of postcode districts in an approximate or non-exact manner.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00d24043e8819090cc473b6c0923d0 |
completed | May 10, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_6a00d1ec12fc81908c514ed088ef8300 |
completed | May 10, 2026, 6:43 p.m. |
Created at: May 3, 2026, 4:06 p.m.