Triple
T7611188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CT postcode area |
E172239
|
entity |
| Predicate | postcodeSystem |
P7766
|
FINISHED |
| Object | UK postcode system |
—
|
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: UK postcode system | Statement: [CT postcode area, postcodeSystem, UK postcode system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postcodeSystem Context triple: [CT postcode area, postcodeSystem, UK postcode system]
-
A.
postalCodeSystem
chosen
Indicates a system that assigns structured postal codes to geographic areas for organizing and routing mail.
-
B.
postalArea
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
-
C.
postalName
Indicates the standardized name or label used for addressing and postal purposes associated with an entity.
-
D.
postalCode
Indicates the numerical or alphanumerical code assigned to a geographic area for mail delivery associated with an entity.
-
E.
alsoServedByPostalCodeSystem
Indicates that the same geographic area or address is additionally covered or identified by another postal code system.
- 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_69c6994f50808190ba228764bb422417 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa221c848190b892ba1caec8d83a |
completed | March 27, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:55 p.m.