Triple
T17048779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helsinki bus network |
E413639
|
entity |
| Predicate | formerOperator |
P179
|
FINISHED |
| Object | HKL |
E1246151
|
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: HKL | Statement: [Helsinki bus network, formerOperator, HKL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HKL Context triple: [Helsinki bus network, formerOperator, HKL]
-
A.
HKL
chosen
HKL is the public transport authority of Helsinki, responsible for operating and managing the city’s metro, tram, and other urban transit services.
-
B.
HCKE
HCKE is the official abbreviation for HC Košice, a professional ice hockey club based in Košice, Slovakia.
-
C.
BKL
BKL is an alternative name for the Big Circle Line, a major circular metro line in Moscow’s rapid transit system.
-
D.
BKL
BKL is the FAA airport code for Burke Lakefront Airport, a public airport located on the shore of Lake Erie in Cleveland, Ohio.
-
E.
HKY
HKY is the three-letter IATA airport code for Hickory Regional Airport in Hickory, North Carolina, USA.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa092f08190a9e37404a9de662c |
completed | April 18, 2026, 7:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0139f17a5481908896c1c6ff326c2f |
completed | May 11, 2026, 2:07 a.m. |
Created at: April 10, 2026, 5:34 a.m.