Triple
T10857133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 37 |
E256295
|
entity |
| Predicate | subclass |
P1244
|
FINISHED |
| Object | Class 37/9 |
E889006
|
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 37/9 | Statement: [British Rail Class 37, subclass, Class 37/9]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Class 37/9 Context triple: [British Rail Class 37, subclass, Class 37/9]
-
A.
Class 37/0
chosen
Class 37/0 is the original batch of British Rail Class 37 diesel-electric locomotives, known for their distinctive design and long service life across the UK rail network.
-
B.
Class 377
Class 377 is a family of electric multiple-unit commuter trains used extensively on suburban and regional services in southern England.
-
C.
Class 387/4
Class 387/4 is a variant of the British Rail Class 387 electric multiple unit trains, designed for high-capacity commuter and regional services on the UK rail network.
-
D.
Class 387/3
Class 387/3 is a subseries of the British Rail Class 387 electric multiple units, built for high-capacity commuter services with modern onboard amenities and performance.
-
E.
Class 319
Class 319 is a type of British dual-voltage electric multiple unit train used primarily for commuter and regional 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751377da88190a7244bb9d6b0c2ec |
completed | April 9, 2026, 7:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e2d6c077608190822d66b23866f5eb |
completed | April 18, 2026, 12:56 a.m. |
Created at: April 8, 2026, 9:20 p.m.