Triple
T11943324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walthamstow Central |
E284230
|
entity |
| Predicate | hasRailCode |
P18202
|
FINISHED |
| Object | WLC |
E955191
|
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: WLC | Statement: [Walthamstow Central, hasRailCode, WLC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WLC Context triple: [Walthamstow Central, hasRailCode, WLC]
-
A.
WLC
chosen
WLC is the National Rail station code for Walthamstow Central railway station in London, England.
-
B.
WCL
WCL is the commonly used abbreviation for the American University Washington College of Law, a prominent law school in Washington, D.C.
-
C.
WLM
WLM (Workload Manager) is an IBM z/OS component that dynamically manages and prioritizes system workloads to meet performance goals and service-level objectives.
-
D.
LWL
LWL is the vehicle registration code assigned to the Włodawa area in eastern Poland.
-
E.
WLO
WLO is the National Rail station code used to identify London Waterloo Underground station in the UK rail network.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9034444488190925a6fa6c856ed08 |
completed | April 10, 2026, 2:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f458cbb08881909a71f0592c9231ae |
completed | May 1, 2026, 7:39 a.m. |
Created at: April 8, 2026, 9:45 p.m.