Triple
T20000929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackpool North |
E494323
|
entity |
| Predicate | stationCode |
P1289
|
FINISHED |
| Object | BPN |
—
|
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: BPN | Statement: [Blackpool North, stationCode, BPN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BPN Context triple: [Blackpool North, stationCode, BPN]
-
A.
BPN
chosen
BPN is the National Rail station code for Blackpool North railway station, a primary rail terminus serving the seaside town of Blackpool in Lancashire, England.
-
B.
BPN
BPN is the IATA airport code for Sultan Aji Muhammad Sulaiman Sepinggan International Airport serving Balikpapan in East Kalimantan, Indonesia.
-
C.
BNP
BNP is the stock ticker symbol for BNP Paribas, a major French international banking and financial services group.
-
D.
BNP
BNP is the acronym commonly used to refer to the National Library of Portugal, the country’s main institution for preserving and providing access to its bibliographic heritage.
-
E.
BNP
BNP is the National Rail station code assigned to Barnstaple railway station in Devon, England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a15f308190a99ac3205f948acb |
completed | April 20, 2026, 5:25 p.m. |
Created at: April 11, 2026, 3:32 p.m.