Triple
T28510985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolton Mail Centre |
E721482
|
entity |
| Predicate | locatedInPostalArea |
P62409
|
FINISHED |
| Object | BL postcode area |
—
|
NE NERFINISHED |
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: BL postcode area | Statement: [Bolton Mail Centre, locatedInPostalArea, BL postcode area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPostalArea Context triple: [Bolton Mail Centre, locatedInPostalArea, BL postcode area]
-
A.
postalAreaIncludes
Indicates that a given postal area geographically contains or covers another specified location or region.
-
B.
isLocatedInAdministrativeArea
Indicates that one entity is situated within the geographic or jurisdictional boundaries of a specified administrative area (such as a city, county, state, or region).
-
C.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
locatedInRegionalDistrict
Indicates that one entity is geographically situated within the boundaries of a specified regional district.
-
E.
hasPostalAssociationWith
chosen
Indicates a relationship in which one entity is connected to another through postal services, such as mail handling, delivery, routing, or shared postal operations.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
Created at: April 28, 2026, 3:12 a.m.