Triple
T26473984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Thomas Assembly Plant |
E665975
|
entity |
| Predicate | drivetrainFocus |
P120029
|
FINISHED |
| Object | rear-wheel drive |
—
|
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: rear-wheel drive | Statement: [St. Thomas Assembly Plant, drivetrainFocus, rear-wheel drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivetrainFocus Context triple: [St. Thomas Assembly Plant, drivetrainFocus, rear-wheel drive]
-
A.
drivetrainCategory
chosen
Indicates the type or classification of a vehicle’s drivetrain system (e.g., FWD, RWD, AWD) associated with an entity.
-
B.
drivetrainFeature
Indicates that an entity has a specific characteristic, component, or capability related to its drivetrain system.
-
C.
drivetrainRole
Indicates the functional role or position an entity has within a drivetrain system (e.g., input, transmission, or output component).
-
D.
drivetrainChangeDescription
Indicates a description of a modification or change made to a vehicle’s drivetrain system.
-
E.
powertrainComponentOf
Indicates that one entity is a component or subsystem that forms part of the powertrain of another entity.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 12:21 a.m.