Triple
T8198092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opel Vizor |
E191484
|
entity |
| Predicate | designFunction |
P4831
|
FINISHED |
| Object | unified front fascia |
—
|
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: unified front fascia | Statement: [Opel Vizor, designFunction, unified front fascia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designFunction Context triple: [Opel Vizor, designFunction, unified front fascia]
-
A.
designMethod
Indicates that one entity is used as the method, approach, or technique by which another entity is designed or created.
-
B.
designUse
chosen
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
C.
designDescription
Indicates that an entity has a textual explanation or summary of its design, structure, or intended configuration.
-
D.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
E.
designModel
Indicates that one entity creates, specifies, or defines the structure or behavior of another entity as a model or blueprint.
- 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5c2341f881908be59c378896e5bc |
completed | March 31, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:42 p.m.