Triple
T14737360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beijing–Tianjin Intercity Railway |
E346247
|
entity |
| Predicate | usesRollingStockType |
P1305
|
FINISHED |
| Object | CRH2 |
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: CRH2 | Statement: [Beijing–Tianjin Intercity Railway, usesRollingStockType, CRH2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CRH2 Context triple: [Beijing–Tianjin Intercity Railway, usesRollingStockType, CRH2]
-
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.
CRH
CRH is the commonly used abbreviation for the Cambridge Redhawks, a Canadian junior ice hockey team based in Cambridge, Ontario.
-
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 a healthcare facility known as Central Regional Hospital, providing medical and surgical services to its surrounding community.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec73264848190be23c5f0260cbe13 |
completed | April 14, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb90378481909a3083680f11101c |
completed | May 8, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.