Triple
T15790596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz CLS Vision |
E382853
|
entity |
| Predicate | previewedConcept |
P463
|
FINISHED |
| Object | four-door coupé |
—
|
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: four-door coupé | Statement: [Mercedes-Benz CLS Vision, previewedConcept, four-door coupé]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previewedConcept Context triple: [Mercedes-Benz CLS Vision, previewedConcept, four-door coupé]
-
A.
featuredConcept
Indicates that one concept is highlighted or given special prominence relative to others in a particular context.
-
B.
primaryConcept
Indicates that one concept is the main or central idea in relation to another concept or context.
-
C.
demonstratedConcept
chosen
Indicates that an entity has shown, illustrated, or made evident a particular concept through example, explanation, or action.
-
D.
conceptualizedFor
Indicates that one entity has been conceived, designed, or mentally framed specifically for use, application, or relevance to another entity.
-
E.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d819c881908bc43a6124a1bb2e |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.