Triple
T1901921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Speed 1 |
E37707
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | HS1 |
E165920
|
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: HS1 | Statement: [High Speed 1, alsoKnownAs, HS1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HS1 Context triple: [High Speed 1, alsoKnownAs, HS1]
-
A.
HS1 Ltd
chosen
HS1 Ltd is the private company that owns and operates the High Speed 1 rail line and associated infrastructure in the United Kingdom.
-
B.
HSL 1
HSL 1 is a Belgian high-speed railway line that forms part of the international route used by Eurostar and other high-speed services between Brussels and neighboring countries.
-
C.
HS
HS is an internationally standardized system of names and numbers used to classify traded products for customs and statistical purposes.
-
D.
HSS
HSS (Home Subscriber Server) is a core network database in IP Multimedia Subsystem (IMS) architectures that manages user identities, subscription profiles, and authentication for telecom services.
-
E.
HESX
HESX is the ICAO airport code assigned to Sphinx International Airport in Egypt.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb18da27c8190b315b462c857f4c2 |
completed | March 7, 2026, 5:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adeaf558148190b920693e2348190f |
completed | March 8, 2026, 9:32 p.m. |
Created at: March 4, 2026, 7:35 p.m.