Triple
T17048781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helsinki bus network |
E413639
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | HSL network |
E410285
|
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: HSL network | Statement: [Helsinki bus network, partOf, HSL network]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HSL network Context triple: [Helsinki bus network, partOf, HSL network]
-
A.
HSL 2
HSL 2 is a Belgian high-speed railway line primarily used for fast passenger services between major cities and international connections.
-
B.
HSL app
chosen
The HSL app is a mobile application that allows users to plan journeys, buy tickets, and access real-time public transport information in the Helsinki region.
-
C.
Nitelink
Nitelink is Dublin’s late-night bus service network, providing after-hours public transport on key routes across the city and suburbs.
-
D.
HSL 3
HSL 3 is a Belgian high-speed railway line that connects Liège to the German border as part of the international high-speed rail corridor between Brussels and Germany.
-
E.
HSL 4
HSL 4 is a Belgian high-speed railway line that connects Antwerp to the Dutch border as part of the international high-speed rail corridor between Brussels and Amsterdam.
- 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_6a012341b8e88190a2bee865be5ca1c1 |
completed | May 11, 2026, 12:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.