Triple
T15264842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super GT |
E364871
|
entity |
| Predicate | drivetrainRegulationGT500 |
P117876
|
FINISHED |
| Object | front-engine 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: front-engine rear-wheel drive | Statement: [Super GT, drivetrainRegulationGT500, front-engine rear-wheel drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivetrainRegulationGT500 Context triple: [Super GT, drivetrainRegulationGT500, front-engine rear-wheel drive]
-
A.
drivingForce
Indicates a causal influence or motivating factor that propels or significantly shapes another process, event, or outcome.
-
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.
valvetrainControl
Indicates a control relationship in which one entity regulates or manages the operation of an engine’s valvetrain system.
-
E.
supportsDrivetrainFeature
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00851c5b88190a296b6a105d3ee30 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:14 a.m.