Triple
T28928894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volkswagen ID.7 |
E733726
|
entity |
| Predicate | hasInfotainmentScreenSize |
P40529
|
FINISHED |
| Object | 15-inch central touchscreen (approx.) |
—
|
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: 15-inch central touchscreen (approx.) | Statement: [Volkswagen ID.7, hasInfotainmentScreenSize, 15-inch central touchscreen (approx.)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfotainmentScreenSize Context triple: [Volkswagen ID.7, hasInfotainmentScreenSize, 15-inch central touchscreen (approx.)]
-
A.
rearScreenSize
Indicates the size or dimensions of a device’s rear display screen.
-
B.
screenDiameter
Indicates the size of a screen measured across its diagonal.
-
C.
screenCapacity
Indicates the maximum number of items or content units that can be displayed on a screen at one time.
-
D.
integratedDisplaySize
chosen
Indicates the size or dimensions of a built-in or non-detachable display associated with an entity.
-
E.
instrumentClusterDisplaySize
Indicates the size of the display used in the instrument cluster of a vehicle.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: April 28, 2026, 8:26 a.m.