Triple
T14061220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRH |
E338350
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | CRH |
E338350
|
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: CRH | Statement: [CRH, abbreviation, CRH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CRH Context triple: [CRH, abbreviation, CRH]
-
A.
CRH
CRH is the commonly used abbreviation for the Cambridge Redhawks, a Canadian junior ice hockey team based in Cambridge, Ontario.
-
B.
CRH
CRH is a healthcare facility known as Central Regional Hospital, providing medical and surgical services to its surrounding community.
-
C.
CRH
chosen
CRH is the China Railway High-speed service and branding used for China's network of high-speed passenger trains.
-
D.
CRH3 EMU
The CRH3 EMU is a high-speed electric multiple unit train used in China’s railway network, derived from Siemens Velaro technology and designed for operation at speeds up to around 350 km/h.
-
E.
CRH380C
The CRH380C is a high-speed electric multiple unit train used in China’s railway network, designed for rapid passenger service at speeds of up to around 380 km/h.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de568876308190840361dcaf10bd45 |
completed | April 14, 2026, 3 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb6654850819083262f3fb981eb1a |
completed | May 7, 2026, 3:57 p.m. |
Created at: April 9, 2026, 10:21 p.m.