Triple
T15292809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Kingdom postcode system |
E365567
|
entity |
| Predicate | postcodeAreaCountApprox |
P117991
|
FINISHED |
| Object | 120 |
—
|
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: 120 | Statement: [United Kingdom postcode system, postcodeAreaCountApprox, 120]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postcodeAreaCountApprox Context triple: [United Kingdom postcode system, postcodeAreaCountApprox, 120]
-
A.
hasPostcodeDistrictsApprox
Indicates that one entity is associated with a set of postcode districts in an approximate or non-exact manner.
-
B.
regionCodeCountApprox
Indicates an approximate count of distinct region codes associated with the given context or dataset.
-
C.
postalArea
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
-
D.
hasPostcodeDistrictCode
Indicates that an entity is associated with a specific postcode district code within a postal addressing system.
-
E.
postalAreaIncludes
Indicates that a given postal area geographically contains or covers another specified location or region.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03682ea488190ac82fdbd0e855d34 |
completed | April 16, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:15 a.m.