Triple
T34602509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Cross Gate depot |
E888503
|
entity |
| Predicate | servicedRollingStock |
P152978
|
FINISHED |
| Object | Class 378 Capitalstar |
—
|
NE NERFINISHED |
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 378 Capitalstar | Statement: [New Cross Gate depot, servicedRollingStock, Class 378 Capitalstar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servicedRollingStock Context triple: [New Cross Gate depot, servicedRollingStock, Class 378 Capitalstar]
-
A.
servicesRollingStock
chosen
Indicates that an entity provides operational services to or performs work on rolling stock (such as trains or rail vehicles).
-
B.
ownedRollingStock
Indicates that one entity possesses or has ownership rights over specific rolling stock (such as trains, railcars, or locomotives).
-
C.
passengerRollingStock
Indicates that the rolling stock is designed or used for carrying passengers rather than freight or other purposes.
-
D.
formerRollingStock
Indicates that an entity was previously used as rolling stock (e.g., railway vehicles) but no longer serves in that capacity.
-
E.
relatedRollingStock
Indicates a relationship between pieces of rolling stock that are associated with each other, such as through shared operations, configurations, or functional linkage.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 2:03 a.m.