Triple
T3740150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GMC Savana van platform |
E79678
|
entity |
| Predicate | layoutOptions |
P51177
|
FINISHED |
| Object | front-engine, rear-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: front-engine, rear-wheel-drive | Statement: [GMC Savana van platform, layoutOptions, front-engine, rear-wheel-drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layoutOptions Context triple: [GMC Savana van platform, layoutOptions, front-engine, rear-wheel-drive]
-
A.
layoutDetail
Indicates the specific arrangement or configuration details of how elements are laid out in relation to each other.
-
B.
layoutEngine
Indicates the rendering or layout system responsible for arranging and positioning elements within a visual or document structure.
-
C.
controlLayout
Indicates that one entity determines or manages the spatial or structural arrangement of another entity.
-
D.
stylePositioning
Indicates how an entity is spatially or visually arranged or aligned relative to a reference frame or other elements.
-
E.
layoutArtist
Indicates a relationship where one entity serves as the layout artist responsible for arranging the visual or graphic elements of 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb5344fc8190b183aca5c04e3bcc |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc198b95481908ca6e4e875aae446 |
completed | March 8, 2026, 6:36 p.m. |
Created at: March 8, 2026, 3:34 p.m.