Triple
T16980703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BT1 |
E411935
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | BT postcode area |
E793723
|
NE 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: BT postcode area | Statement: [BT1, partOf, BT postcode area]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BT postcode area Context triple: [BT1, partOf, BT postcode area]
-
A.
BT postcode area
chosen
The BT postcode area is the group of postal districts covering Belfast and the majority of Northern Ireland.
-
B.
BN postcode area
The BN postcode area is a group of postal districts in southern England, primarily covering Brighton and surrounding parts of East and West Sussex.
-
C.
PA postcode area
The PA postcode area is a group of postal districts in western Scotland, covering towns such as Paisley and parts of Renfrewshire and Argyll and Bute.
-
D.
HP postcode area
The HP postcode area is a group of postal districts in the United Kingdom centered on High Wycombe and surrounding parts of Buckinghamshire and nearby counties.
-
E.
TW postcode area
The TW postcode area, also known as the Twickenham postcode area, covers Twickenham and surrounding parts of southwest London and north Surrey.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d18776c081909225620fd43aca57 |
completed | April 18, 2026, 6:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d479610c8190a6281e6d4959b820 |
completed | May 10, 2026, 6:54 p.m. |
Created at: April 10, 2026, 5:32 a.m.