Triple
T18861188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | i-Cockpit interior design |
E461313
|
entity |
| Predicate | instrumentClusterType |
P133212
|
FINISHED |
| Object | digital instrument cluster in many models |
—
|
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: digital instrument cluster in many models | Statement: [i-Cockpit interior design, instrumentClusterType, digital instrument cluster in many models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instrumentClusterType Context triple: [i-Cockpit interior design, instrumentClusterType, digital instrument cluster in many models]
-
A.
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.
-
B.
instrumentClusterPosition
Indicates the spatial location or mounting position of an instrument cluster relative to a reference point in a system or vehicle.
-
C.
instrumentClusterDisplaySize
Indicates the size of the display used in the instrument cluster of a vehicle.
-
D.
typeOfInstallation
Indicates the specific kind or category of installation associated with an entity (e.g., how or in what form something is installed).
-
E.
typicalCircuitType
Indicates that one entity is the usual or standard type of circuit associated with another 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c060bfc4819092ac591692a6ccd5 |
completed | April 20, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:57 a.m.