Triple
T32608686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lohner-Porsche Mixte Hybrid |
E833593
|
entity |
| Predicate | usesElectricMotorType |
P8442
|
FINISHED |
| Object | in-wheel electric motors |
—
|
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: in-wheel electric motors | Statement: [Lohner-Porsche Mixte Hybrid, usesElectricMotorType, in-wheel electric motors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesElectricMotorType Context triple: [Lohner-Porsche Mixte Hybrid, usesElectricMotorType, in-wheel electric motors]
-
A.
hasElectricMotor
Indicates that an entity is equipped with, contains, or uses an electric motor as part of its operation or structure.
-
B.
electricMotorType
chosen
Indicates the specific kind or category of electric motor associated with an entity.
-
C.
isElectrically
Indicates that one entity has an electrical property, connection, or interaction in relation to another entity.
-
D.
hasDrivingMotorCar
Indicates that one entity operates or drives a motor car in relation to another entity or context.
-
E.
motorizedUse
Indicates that an entity is used or operated by means of a motor or engine, rather than by human or animal power.
- 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.