Triple
T35812729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WD postcode area |
E1035273
|
entity |
| Predicate | mailSortingSystem |
P169037
|
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: [WD postcode area, mailSortingSystem, UK postcode system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mailSortingSystem Context triple: [WD postcode area, mailSortingSystem, UK postcode system]
-
A.
mainSortingOffice
Indicates that one entity serves as the primary or central sorting office responsible for handling and routing items (typically mail or packages) for another entity or area.
-
B.
mailRoute
Indicates a route or path along which mail or postal items are transported between locations.
-
C.
mailboxModel
Indicates a relationship where an entity functions as or is associated with a specific mailbox configuration or structural model.
-
D.
mailCollectedFrom
Indicates that mail has been picked up or retrieved from a specified source or location.
-
E.
mailSystemType
chosen
Indicates the type or category of mail system associated with or used by 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.