Triple
T18877811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiat 1300/1500 |
E461733
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automobile model family |
C1018
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: automobile model family Context triple: [Fiat 1300/1500, instanceOf, automobile model family]
-
A.
automobile model
chosen
An automobile model is a specific version of a vehicle produced by a manufacturer, defined by a distinct combination of design, features, and specifications that differentiates it from other vehicles in the product lineup.
-
B.
automobile engine family
A group of related automobile engines that share a common design architecture, components, and core specifications, but may vary in displacement, tuning, or configuration to suit different vehicles or performance requirements.
-
C.
automobile engine family
A group of related automobile engines that share a common design architecture, components, and engineering characteristics, often varying only in displacement, tuning, or minor features.
-
D.
automotive engine family
An automotive engine family is a group of closely related internal combustion engines that share a common basic design, architecture, and components but differ in specific parameters such as displacement, tuning, or fuel system to suit various vehicle applications.
-
E.
automobile model variant
An automobile model variant is a specific version of a car model distinguished by particular features, options, performance characteristics, or styling differences within the same overall model line.
- F. None of above.
Provenance (1 batch)
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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:57 a.m.