Triple
T9256149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEAT Arona |
E222447
|
entity |
| Predicate | infotainmentScreenSize |
P40529
|
FINISHED |
| Object | up to 9.2 inches |
—
|
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: up to 9.2 inches | Statement: [SEAT Arona, infotainmentScreenSize, up to 9.2 inches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infotainmentScreenSize Context triple: [SEAT Arona, infotainmentScreenSize, up to 9.2 inches]
-
A.
integratedDisplaySize
chosen
Indicates the size or dimensions of a built-in or non-detachable display associated with an entity.
-
B.
screenCurvature
Indicates that one entity has a specific degree or type of curvature in its screen surface relative to another entity or a defined standard.
-
C.
externalDisplaySize
Indicates the size or dimensions of an external display associated with an entity.
-
D.
displayResolution
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
-
E.
availableDisplaySizes
Indicates the set of display size options that can be provided or used for a given entity.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd06b4e2048190af0d65b904677c36 |
completed | April 1, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:32 p.m.