Triple
T9896485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opel Mokka |
E182186
|
entity |
| Predicate | faceliftOrRedesign |
P45252
|
FINISHED |
| Object | 2020 redesign |
—
|
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: 2020 redesign | Statement: [Opel Mokka, faceliftOrRedesign, 2020 redesign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faceliftOrRedesign Context triple: [Opel Mokka, faceliftOrRedesign, 2020 redesign]
-
A.
faceliftOf
chosen
Indicates that one entity is a redesigned, updated, or cosmetically improved version of another existing entity.
-
B.
facelift
Indicates that an entity undergoes a cosmetic surgical procedure intended to tighten or rejuvenate its facial appearance.
-
C.
faceliftFeature
Indicates that one entity is a specific feature, component, or aspect involved in a facelift procedure or facelift-related modification of the other entity.
-
D.
designerOfFacelift
Indicates that one entity is the designer or creator responsible for the facelift (a redesign or cosmetic update) of another entity.
-
E.
redesigned
Indicates that an entity has been modified or created anew in terms of its structure, appearance, or functionality, replacing a previous design.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4a9d2f4819086cfdd42b613cd8c |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.