Triple
T1979857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 Motor Trend Car of the Year |
E42999
|
entity |
| Predicate | winnerBodyStyle |
P35740
|
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: [2013 Motor Trend Car of the Year, winnerBodyStyle, sedan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerBodyStyle Context triple: [2013 Motor Trend Car of the Year, winnerBodyStyle, sedan]
-
A.
winnerRepresents
Indicates that the winner of a competition or contest serves as a representative for a particular group, organization, or entity.
-
B.
winnerState
Indicates the state or condition of an entity that has achieved victory or been declared the winner in a given context.
-
C.
winnerTitle
Indicates the formal title or designation awarded to the entity that wins a particular competition, contest, or event.
-
D.
wonTitleWith
Indicates that an entity secured a specific title, award, or championship while being associated with or representing another entity (such as a team, organization, or group).
-
E.
wonFor
Indicates that one entity received an award, prize, or recognition specifically on behalf of or representing another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69abb96e07c08190beed60096e9d71b4 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:36 p.m.