Triple
T11399298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRH2 EMU |
E270063
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | CRH2G |
E270063
|
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: CRH2G | Statement: [CRH2 EMU, hasVariant, CRH2G]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CRH2G Context triple: [CRH2 EMU, hasVariant, CRH2G]
-
A.
CRH2 EMU
chosen
The CRH2 EMU is a high-speed electric multiple unit train used in China’s railway network, derived from Japan’s Shinkansen technology and designed for fast, long-distance passenger service.
-
B.
CRH6A EMU
The CRH6A EMU is a high-speed electric multiple unit train used in China for intercity passenger services.
-
C.
CRH380A EMU
The CRH380A EMU is a high-speed electric multiple unit train used in China’s railway network, designed for rapid intercity passenger service at speeds of up to around 380 km/h.
-
D.
CRH
CRH is the China Railway High-speed service and branding used for China's network of high-speed passenger trains.
-
E.
CRH
CRH is the commonly used abbreviation for the Cambridge Redhawks, a Canadian junior ice hockey team based in Cambridge, Ontario.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d8001adc188190ae45227856156412 |
completed | April 9, 2026, 7:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5d3470e208190aef43936bac2e4e9 |
completed | April 20, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:34 p.m.