Triple
T33406427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 World Car Design of the Year |
E855448
|
entity |
| Predicate | winnerDesignerBrand |
P184032
|
FINISHED |
| Object | Hyundai Motor Company |
—
|
NE NERFINISHED |
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: Hyundai Motor Company | Statement: [2022 World Car Design of the Year, winnerDesignerBrand, Hyundai Motor Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerDesignerBrand Context triple: [2022 World Car Design of the Year, winnerDesignerBrand, Hyundai Motor Company]
-
A.
designerAlias
Indicates that one name or label is used as an alternative alias for a designer.
-
B.
beltDesignOwner
Indicates that a particular entity is the owner or rights holder of a specific belt design.
-
C.
designerType
Indicates the specific kind or category of designer role associated with an entity.
-
D.
designedBy
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
E.
vendorDesignation
Indicates that one entity assigns or recognizes a specific vendor status, label, or role for another entity within a business or procurement context.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 1, 2026, 1:36 a.m.