Triple
T16812280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNER Azuma |
E408643
|
entity |
| Predicate | trainClass |
P56947
|
FINISHED |
| Object | Class 801 |
E1236089
|
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: Class 801 | Statement: [LNER Azuma, trainClass, Class 801]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Class 801 Context triple: [LNER Azuma, trainClass, Class 801]
-
A.
Class 801
chosen
Class 801 is a type of Hitachi-built high-speed electric multiple unit used in the UK as part of the Azuma fleet operated on the East Coast Main Line.
-
B.
Class 802
Class 802 is a type of British high-speed bi-mode multiple unit train used on intercity services, closely related to the Hitachi A-train family.
-
C.
Class 321
Class 321 is a type of British electric multiple unit train widely used for suburban and commuter rail services in the UK.
-
D.
Class 319
Class 319 is a type of British dual-voltage electric multiple unit train used primarily for commuter and regional services.
-
E.
IE 8100 Class
The IE 8100 Class is a series of electric multiple unit trains operated by Iarnród Éireann for Dublin’s DART suburban rail services.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2df5c888190a462614e1432c357 |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c79cdf9c8190aa20d536ca17ab81 |
completed | May 10, 2026, 5:59 p.m. |
Created at: April 10, 2026, 5:23 a.m.