Triple
T13376970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet Cobalt |
E319211
|
entity |
| Predicate | layoutCategory |
P109677
|
FINISHED |
| Object | 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-wheel-drive layout | Statement: [Chevrolet Cobalt, layoutCategory, front-wheel-drive layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layoutCategory Context triple: [Chevrolet Cobalt, layoutCategory, front-wheel-drive layout]
-
A.
styleBoxCategory
Indicates a classification relationship where a style box is assigned to a specific category or type.
-
B.
catalogCategory
Indicates that an item or entity is assigned to, or belongs within, a specific catalog category.
-
C.
layoutDetail
Indicates the specific arrangement or configuration details of how elements are laid out in relation to each other.
-
D.
categoryStructure
Indicates the hierarchical or organizational relationship that defines how categories are structured and arranged relative to one another.
-
E.
sampleCategory
Indicates that an item or instance belongs to, or is classified under, a particular sample category.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce3fec48190a5443d87c85477a3 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:33 p.m.