Triple
T5620676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-car platform |
E147592
|
entity |
| Predicate | automotiveLayout |
P5253
|
FINISHED |
| Object | front-engine, front-wheel-drive layout |
—
|
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, front-wheel-drive layout | Statement: [K-car platform, automotiveLayout, front-engine, front-wheel-drive layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: automotiveLayout Context triple: [K-car platform, automotiveLayout, front-engine, front-wheel-drive layout]
-
A.
vehicleLayout
chosen
Indicates how the components or seating within a vehicle are arranged or configured relative to each other.
-
B.
chassisConstruction
Indicates how the chassis of an object is built or assembled, specifying the construction method or structural design used.
-
C.
powertrainLocation
Indicates the physical placement or mounting position of a vehicle’s powertrain relative to the rest of the vehicle.
-
D.
enginePlacement
Indicates the spatial or structural position where an engine is located or mounted relative to another object or system.
-
E.
chassis
Indicates that one entity serves as the structural frame or supporting base (chassis) for another entity.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02211c8f4819090d19656c6eac2d4 |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.