Triple
T34710486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tempest Custom |
E1000629
|
entity |
| Predicate | bodyStyleFamily |
P74532
|
FINISHED |
| Object | front-engine, rear-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, rear-wheel-drive layout | Statement: [Tempest Custom, bodyStyleFamily, front-engine, rear-wheel-drive layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyStyleFamily Context triple: [Tempest Custom, bodyStyleFamily, front-engine, rear-wheel-drive layout]
-
A.
styleFamily
Indicates that one style is grouped within the same stylistic family or category as another style.
-
B.
bodyStyleCategory
chosen
Indicates the general body style classification or category that an item (such as a vehicle or product) belongs to.
-
C.
bodyStyleProduced
Indicates that a particular body style was manufactured or produced by a given entity (such as a company, plant, or production line).
-
D.
primaryBodyStyle
Indicates the main or predominant body configuration or structural form associated with an entity.
-
E.
bodyStyleHistory
Indicates the historical record of changes or versions in an entity’s body style over time.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.