Triple
T23632831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 142 |
E583661
|
entity |
| Predicate | bodyDesignDerivedFrom |
P153344
|
FINISHED |
| Object | Leyland National bus |
—
|
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: Leyland National bus | Statement: [British Rail Class 142, bodyDesignDerivedFrom, Leyland National bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyDesignDerivedFrom Context triple: [British Rail Class 142, bodyDesignDerivedFrom, Leyland National bus]
-
A.
carbodyMaterial
Indicates the material from which a vehicle’s body or main structural shell is made.
-
B.
chassisMaterialFeature
Indicates that an entity has a chassis characterized by a specific material-related feature or property.
-
C.
chassisDesigner
Indicates that one entity is the designer or creator responsible for the chassis of another entity.
-
D.
chassisOrigin
Indicates the place or source from which a chassis was originally produced, manufactured, or derived.
-
E.
bodyStyleProduced
Indicates that a particular body style was manufactured or produced by a given entity (such as a company, plant, or production line).
- F. None of above. chosen
Provenance (4 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1e90a6881909f19b2446f9d54f0 |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f138b8c9248190b059bc38a9a50958 |
completed | April 28, 2026, 10:46 p.m. |
Created at: April 17, 2026, 6:47 p.m.