Triple
T29203534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alstom Class 460 |
E740345
|
entity |
| Predicate | enteredServiceForGatwickExpress |
P128767
|
FINISHED |
| Object | 2000 |
—
|
LITERAL 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: 2000 | Statement: [Alstom Class 460, enteredServiceForGatwickExpress, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredServiceForGatwickExpress Context triple: [Alstom Class 460, enteredServiceForGatwickExpress, 2000]
-
A.
enteredServiceOnElizabethLine
Indicates that something (typically a train, station, or service) began operating or was officially introduced into service on the Elizabeth Line.
-
B.
enteredServiceOn
Indicates the date or time when an entity first began active use, operation, or service.
-
C.
enteredServiceOnRoute
chosen
Indicates that an entity (typically a vehicle or service) began operating on a specific route starting from a particular date or time.
-
D.
primaryLondonTerminal
Indicates that a given station serves as the main London terminal for a particular rail service or route.
-
E.
secondaryLondonTerminal
Indicates that a location serves as a secondary terminal in London associated with a primary London terminal for a given service or route.
- F. None of above.
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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 12:08 p.m.