Triple
T22017325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 325 |
E543745
|
entity |
| Predicate | hasDrivingCabAt |
P89793
|
FINISHED |
| Object | each end of unit |
—
|
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: each end of unit | Statement: [British Rail Class 325, hasDrivingCabAt, each end of unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrivingCabAt Context triple: [British Rail Class 325, hasDrivingCabAt, each end of unit]
-
A.
hasCabType
Indicates that an entity is associated with or characterized by a specific type or category of cab.
-
B.
hasDrivingMotorCar
Indicates that one entity operates or drives a motor car in relation to another entity or context.
-
C.
hasCabPosition
chosen
Indicates that an entity has a specific position or placement of a cab relative to its overall structure or configuration.
-
D.
canDrive
Indicates that one entity has the ability or permission to operate a vehicle or drive another entity.
-
E.
hasVehicleFeature
Indicates that a vehicle possesses, includes, or is equipped with a specific feature or characteristic.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127c4e0088190a5241d1b87d746da |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:23 p.m.