Triple
T1979856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 Motor Trend Car of the Year |
E42999
|
entity |
| Predicate | hasWinningModelYear |
P4161
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [2013 Motor Trend Car of the Year, hasWinningModelYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWinningModelYear Context triple: [2013 Motor Trend Car of the Year, hasWinningModelYear, 2013]
-
A.
modelYears
chosen
Indicates the association between a product (often a vehicle or device) and the specific calendar years in which that model version was produced or marketed.
-
B.
lastModelProduced
Indicates that one entity is the most recently created or generated model associated with another entity.
-
C.
modelProduced
Indicates that a particular model has generated or produced a specified output, result, or artifact.
-
D.
hasTypeOfYear
Indicates that a given year is classified as belonging to a specific type or category of year (e.g., fiscal, academic, leap).
-
E.
hasFranchiseModel
Indicates that one entity operates under, offers, or is associated with a business franchise system or structure defined by another entity.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb96f932881908bebfc4176fda7c0 |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb798d288819083132cf14605bd02 |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:36 p.m.