Triple
T32272922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Preston postcode area |
E824461
|
entity |
| Predicate | majorPostTown |
P2711
|
FINISHED |
| Object | Preston |
—
|
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: Preston | Statement: [Preston postcode area, majorPostTown, Preston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorPostTown Context triple: [Preston postcode area, majorPostTown, Preston]
-
A.
postTown
chosen
Indicates the town or locality that serves as the postal address destination for a given address or location.
-
B.
majorAccessTown
Indicates that a location serves as a primary or significant access point to a town, such as a main route, gateway, or connection hub.
-
C.
primaryTown
Indicates that a given town is the main or most important town associated with an entity (such as a person, organization, or region).
-
D.
mainTownOn
Indicates that one town is the primary or principal town located on or associated with a particular geographic feature, route, or area.
-
E.
majorTownInRegion
Indicates that a town is one of the principal or most significant towns within a specified region.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: May 1, 2026, 12:42 a.m.