Triple
T16789900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyundai Ioniq 6 |
E408078
|
entity |
| Predicate | instrumentClusterDisplaySize |
P124641
|
FINISHED |
| Object | 12.3 inch digital cluster |
—
|
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: 12.3 inch digital cluster | Statement: [Hyundai Ioniq 6, instrumentClusterDisplaySize, 12.3 inch digital cluster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instrumentClusterDisplaySize Context triple: [Hyundai Ioniq 6, instrumentClusterDisplaySize, 12.3 inch digital cluster]
-
A.
integratedDisplaySize
Indicates the size or dimensions of a built-in or non-detachable display associated with an entity.
-
B.
coverDisplaySize
Indicates the size of a device’s secondary (cover) display in physical units, such as inches or centimeters.
-
C.
combinedDisplaySize
Indicates the total display area resulting from combining the screen sizes of multiple devices or components.
-
D.
instrumentCluster
Indicates a relationship where one entity serves as a set or group of instruments or tools used by another entity to perform an action or function.
-
E.
externalDisplaySize
Indicates the size or dimensions of an external display associated with an entity.
- F. None of above. chosen
Provenance (4 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a50e18819090a30e1f38e520e0 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326bac94481908c082117553320f8 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:22 a.m.