Triple
T833717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perkins CV12-6A |
E18022
|
entity |
| Predicate | drivetrainRole |
P20169
|
FINISHED |
| Object | drives Challenger 2 powerpack |
—
|
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: drives Challenger 2 powerpack | Statement: [Perkins CV12-6A, drivetrainRole, drives Challenger 2 powerpack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivetrainRole Context triple: [Perkins CV12-6A, drivetrainRole, drives Challenger 2 powerpack]
-
A.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
B.
powertrainLocation
Indicates the physical placement or mounting position of a vehicle’s powertrain relative to the rest of the vehicle.
-
C.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
D.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
-
E.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb84fe081909b8f4b4202845860 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7b3d2481909199f7c9f305bdfe |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab60fea8819098ce3269181897d1 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:38 p.m.