Triple
T32608700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lohner-Porsche Mixte Hybrid |
E833593
|
entity |
| Predicate | wheelMotorLocation |
P129931
|
FINISHED |
| Object | front wheels |
—
|
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 wheels | Statement: [Lohner-Porsche Mixte Hybrid, wheelMotorLocation, front wheels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wheelMotorLocation Context triple: [Lohner-Porsche Mixte Hybrid, wheelMotorLocation, front wheels]
-
A.
motorPlacement
chosen
Indicates the spatial position or mounting configuration of a motor relative to the system or components it drives.
-
B.
electricMotorPosition
Indicates the rotational position or angle of an electric motor at a given moment.
-
C.
motorPosition
Indicates the specific location or angle at which a motor’s moving component is currently set.
-
D.
wheelDrivePosition
Indicates the position or configuration of the drive mechanism relative to the vehicle’s wheels (e.g., front-, rear-, or all-wheel drive).
-
E.
powertrainLocation
Indicates the physical placement or mounting position of a vehicle’s powertrain relative to the rest of the vehicle.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c6c91a1c819097d51d2a159e223b |
completed | May 3, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:05 a.m.