Triple
T8866158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche 918 Spyder |
E211022
|
entity |
| Predicate | steeringSystem |
P19324
|
FINISHED |
| Object | rear-axle steering |
—
|
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-axle steering | Statement: [Porsche 918 Spyder, steeringSystem, rear-axle steering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: steeringSystem Context triple: [Porsche 918 Spyder, steeringSystem, rear-axle steering]
-
A.
steeringType
chosen
Indicates the kind or mechanism of steering control used to direct the movement of an entity.
-
B.
hasSteering
Indicates that one entity is equipped with or possesses a steering mechanism that allows control of its direction.
-
C.
steeringWheelPosition
Indicates the relative location or orientation of a steering wheel with respect to a reference point, such as a vehicle’s interior layout or driving side.
-
D.
driveMechanism
Indicates the mechanism or component that transmits power to drive or actuate another part of a system.
-
E.
requiresControlSystem
Indicates that one entity depends on or mandates the presence of a control system associated with another entity in order to function or be valid.
- 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_69ca838d3c7c8190a849566d5afd2b11 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6106d41081909db710bda8aaf6fd |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:51 p.m.