Triple
T19176946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TA24 |
E469464
|
entity |
| Predicate | postcodeAreaType |
P1093
|
FINISHED |
| Object | geographic postcode area |
—
|
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: geographic postcode area | Statement: [TA24, postcodeAreaType, geographic postcode area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postcodeAreaType Context triple: [TA24, postcodeAreaType, geographic postcode area]
-
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.
postalCodeType
chosen
Indicates the classification or type category assigned to a given postal code.
-
C.
postalAreaIncludes
Indicates that a given postal area geographically contains or covers another specified location or region.
-
D.
hasPostcodeDistrictCode
Indicates that an entity is associated with a specific postcode district code within a postal addressing system.
-
E.
postcodeAreaCountApprox
Indicates an approximate count of postcode areas 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f618f18c8190b98995fda4b6fea0 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.