Triple
T30038829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche Ceramic Composite Clutch |
E763238
|
entity |
| Predicate | intendedVehicleLayout |
P187575
|
FINISHED |
| Object | mid-engine sports car |
—
|
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: mid-engine sports car | Statement: [Porsche Ceramic Composite Clutch, intendedVehicleLayout, mid-engine sports car]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedVehicleLayout Context triple: [Porsche Ceramic Composite Clutch, intendedVehicleLayout, mid-engine sports car]
-
A.
vehicleLayout
Indicates how the components or seating within a vehicle are arranged or configured relative to each other.
-
B.
vehicleLayoutCompatibility
Indicates that two vehicle-related components or systems are suitable to be arranged or integrated together within a given vehicle layout.
-
C.
intendedVehicle
Indicates that one entity is the vehicle that another entity plans or is meant to use.
-
D.
hasLeadingWheelArrangement
Indicates the specific configuration of the leading (front) wheels in a vehicle’s or locomotive’s wheel arrangement.
-
E.
intendedForVehicle
Indicates that something is designed, meant, or suitable to be used with or by a particular vehicle.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb6fdab95c81909acff3c6a2359787 |
completed | May 6, 2026, 4:44 p.m. |
Created at: April 29, 2026, 6:52 p.m.