Triple
T3523085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KT postcode area |
E74471
|
entity |
| Predicate | containsPostcodeDistrict |
P32592
|
FINISHED |
| Object | KT1 |
—
|
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: KT1 | Statement: [KT postcode area, containsPostcodeDistrict, KT1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPostcodeDistrict Context triple: [KT postcode area, containsPostcodeDistrict, KT1]
-
A.
containsDistrictMunicipality
Indicates that an administrative region includes one or more district municipalities within its boundaries.
-
B.
postalAreaIncludes
chosen
Indicates that a given postal area geographically contains or covers another specified location or region.
-
C.
includesDistrict
Indicates that one administrative or geographic entity contains or encompasses a specific district within its boundaries.
-
D.
hasPostalCodePrefix
Indicates that a location’s postal code begins with a specified sequence of characters.
-
E.
postalArea
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc4f16b8819094ad2755670ddc7b |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.