Triple
T13290562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz MFA platform |
E316549
|
entity |
| Predicate | layoutSupport |
P109346
|
FINISHED |
| Object | all-wheel drive |
—
|
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: all-wheel drive | Statement: [Mercedes-Benz MFA platform, layoutSupport, all-wheel drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layoutSupport Context triple: [Mercedes-Benz MFA platform, layoutSupport, all-wheel drive]
-
A.
layoutCompatibility
Indicates that two layouts can coexist or be used interchangeably without causing conflicts or usability issues.
-
B.
layoutDetail
Indicates the specific arrangement or configuration details of how elements are laid out in relation to each other.
-
C.
layoutOptions
Indicates how elements are arranged or positioned relative to each other within a given space or structure.
-
D.
layoutEngine
Indicates the rendering or layout system responsible for arranging and positioning elements within a visual or document structure.
-
E.
supportedView
Indicates that one entity provides or enables a particular view, perspective, or representation that is available for use by another entity.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:27 p.m.