Triple
T28807716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trendline |
E727424
|
entity |
| Predicate | bodyStylesAvailable |
P51843
|
FINISHED |
| Object | sedan |
—
|
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: sedan | Statement: [Trendline, bodyStylesAvailable, sedan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyStylesAvailable Context triple: [Trendline, bodyStylesAvailable, sedan]
-
A.
bodyStyleCategory
Indicates the general body style classification or category that an item (such as a vehicle or product) belongs to.
-
B.
bodyStyleProduced
Indicates that a particular body style was manufactured or produced by a given entity (such as a company, plant, or production line).
-
C.
associatedWithBodyStyles
Indicates a relationship where something (such as a product, model, or item) is linked or connected to one or more specific body styles.
-
D.
offersBodyStyle
chosen
Indicates that an entity (such as a manufacturer or model line) makes a particular vehicle body style available as an option.
-
E.
bodyVariant
Indicates that one entity is an alternative physical form or version of another entity’s body.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:29 a.m.