Triple
T32232550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poole railway station |
E823378
|
entity |
| Predicate | hasStationPostcode |
P75298
|
FINISHED |
| Object | BH15 |
—
|
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: BH15 | Statement: [Poole railway station, hasStationPostcode, BH15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStationPostcode Context triple: [Poole railway station, hasStationPostcode, BH15]
-
A.
hasPostcodeSector
Indicates that an entity is associated with a specific postcode sector within a postal addressing system.
-
B.
hasPostcodeAreasAlong
Indicates that a geographic feature or route is associated with, or passes through, specific postcode areas along its extent.
-
C.
hasStationCode
Indicates that an entity is associated with a specific station identification code.
-
D.
hasPostcodeAreaNow
Indicates that an entity is currently located within, or associated with, a specific postcode area.
-
E.
hasPostcodeDistrictCode
chosen
Indicates that an entity is associated with a specific postcode district code within a postal addressing system.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 1, 2026, 12:39 a.m.