Triple
T12717840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willesden Junction |
E303894
|
entity |
| Predicate | stationCode |
P1289
|
FINISHED |
| Object | WIJ |
E888507
|
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: WIJ | Statement: [Willesden Junction, stationCode, WIJ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WIJ Context triple: [Willesden Junction, stationCode, WIJ]
-
A.
WIJ
chosen
WIJ is the National Rail station code for Willesden Junction, a major interchange station in northwest London served by both Overground and mainline rail services.
-
B.
WIE
WIE is the IATA airport code for Wiesbaden Air Base, a military airfield located near Wiesbaden, Germany.
-
C.
WIL
WIL is the standard abbreviation used for the Wilmington Blue Rocks minor league baseball team.
-
D.
WIL
WIL is the IATA airport code for Wilson Airport, a busy domestic and regional airport serving Nairobi, Kenya.
-
E.
WID
WID is the National Rail station code assigned to Widnes railway station in Cheshire, England.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9620bd6148190a2f50067a4c18c14 |
completed | April 10, 2026, 8:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f671bcc10481909f150989f9545752 |
completed | May 2, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:23 p.m.