Triple
T5886317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunbridge Wells Central |
E130871
|
entity |
| Predicate | hasStationCode |
P1289
|
FINISHED |
| Object | TBW |
E126970
|
NE 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: TBW | Statement: [Tunbridge Wells Central, hasStationCode, TBW]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TBW Context triple: [Tunbridge Wells Central, hasStationCode, TBW]
-
A.
TBW
chosen
TBW is the National Rail station code for Tunbridge Wells railway station in Kent, England.
-
B.
TB
TB is the standard abbreviation for the Tampa Bay Rays, a Major League Baseball team based in St. Petersburg, Florida.
-
C.
TWB
TWB is the IATA airport code for Toowoomba City Aerodrome, a regional airport serving the city of Toowoomba in Queensland, Australia.
-
D.
TBU
TBU is the vehicle registration code assigned to cars registered in the Busko-Zdrój area of Poland.
-
E.
TIB
TIB is a major German academic institution and library specializing in science and technology information, including digital and research data services.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c0085628dc8190b334c1b44c067efc |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03678dd2c819095926f80f25696b0 |
completed | March 22, 2026, 6:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0b13ce8788190b07771180f0fa376 |
completed | March 23, 2026, 3:19 a.m. |
Created at: March 22, 2026, 3:57 p.m.