Triple

T37291208
Position Surface form Disambiguated ID Type / Status
Subject Micro800 E925668 entity
Predicate supportsHMIIntegration GENERATED
Object PanelView 800 UNRECOGNIZED GENERATED

How this triple was built (1 step)

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.

PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsHMIIntegration
Context triple: [Micro800, supportsHMIIntegration, PanelView 800]
  • A. hasModeIntegration
    Indicates that one entity is integrated with, or supports integration of, a particular mode, method, or modality of operation.
  • B. supportsTransportIntegrationWith
    Indicates that one entity enables or is compatible with the integration of transport or transportation-related systems, services, or data with another entity.
  • C. vehicleIntegration
    Indicates the relationship by which a system, component, or service is incorporated into and made to work cohesively with a vehicle’s hardware, software, or operational environment.
  • D. automotiveClassSupported
    Indicates that a particular automotive class or category is supported or compatible within a given context or system.
  • E. hasLandscapeIntegration
    Indicates that an entity is designed or arranged in a way that it harmoniously fits into, interacts with, or complements its surrounding landscape.
  • F. None of above. chosen

Provenance (1 batch)

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_69f76eb0f86c819098dee07393e69ec3 completed May 3, 2026, 3:50 p.m.
Created at: May 3, 2026, 4:16 p.m.