Triple
T7305652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 720 |
E167966
|
entity |
| Predicate | family |
P566
|
FINISHED |
| Object | Aventra |
E561640
|
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: Aventra | Statement: [British Rail Class 720, family, Aventra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aventra Context triple: [British Rail Class 720, family, Aventra]
-
A.
Aventra
chosen
Aventra is a family of modern electric multiple-unit trains designed and built by Bombardier Transportation (now Alstom) for use on the UK rail network.
-
B.
Electrostar
Electrostar is a widely used family of British electric multiple-unit commuter trains built by Bombardier for suburban and regional services.
-
C.
Siemens Desiro
Siemens Desiro is a family of modern diesel and electric multiple-unit trains widely used for regional and commuter rail services across Europe and beyond.
-
D.
Voyager trains
Voyager trains are a family of high-speed diesel-electric multiple unit passenger trains widely used on intercity services in the UK rail network.
-
E.
MARC Train
MARC Train is a commuter rail service operating in Maryland and the surrounding region, connecting cities such as Washington, D.C., Baltimore, and Martinsburg.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebd61c0c8190abb1368c9dfb1550 |
completed | March 27, 2026, 8:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7e5603a288190a19d426905781cae |
completed | March 28, 2026, 2:27 p.m. |
Created at: March 27, 2026, 3:01 p.m.