Triple
T11909193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liverpool Street station |
E283348
|
entity |
| Predicate | hasIataCode |
P2569
|
FINISHED |
| Object | ZLS |
E636415
|
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: ZLS | Statement: [Liverpool Street station, hasIataCode, ZLS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ZLS Context triple: [Liverpool Street station, hasIataCode, ZLS]
-
A.
ZLS
chosen
ZLS is the IATA airport code assigned to a specific airfield or airport associated with the location abbreviated as LST.
-
B.
ZL
ZL is the IATA airline designator used by Rex Airlines, a regional carrier based in Australia.
-
C.
ZL
ZL is the official station code used to identify Zwolle railway station in the Netherlands’ rail network.
-
D.
ZS
ZS is the vehicle registration code assigned to cars registered in the Polish city of Szczecin.
-
E.
ZS
ZS is the stock ticker symbol for Zscaler, a cloud-based information security company traded on the NASDAQ.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e5278eb081909a7ecfe38beeeda9 |
completed | April 10, 2026, 11:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f418543258819083b49a5bbdc520cd |
completed | May 1, 2026, 3:04 a.m. |
Created at: April 8, 2026, 9:44 p.m.