Triple

T14756639
Position Surface form Disambiguated ID Type / Status
Subject Cadillac User Experience E346745 entity
Predicate controlsSystem P115681 FINISHED
Object audio system 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: audio system | Statement: [Cadillac User Experience, controlsSystem, audio system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: controlsSystem
Context triple: [Cadillac User Experience, controlsSystem, audio system]
  • A. controlMethods
    Indicates the methods or techniques used by one entity to direct, regulate, or influence the behavior, operation, or state of another entity.
  • B. controlsWith
    Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
  • C. exportControl
    Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
  • D. requiresControlSystem
    Indicates that one entity depends on or mandates the presence of a control system associated with another entity in order to function or be valid.
  • E. controlStatus
    Indicates that one entity has a particular level, state, or condition of control over another entity or process.
  • 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_69d822e8896c819091169882f9b20486 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec7ef0fd48190bd4a8af128ef274c completed April 14, 2026, 11:04 p.m.
PD Predicate disambiguation batch_69de8c02e5c08190943c27594026faf7 completed April 14, 2026, 6:48 p.m.
PDg Predicate description generation batch_69de8f4b67cc8190b84b59fcec5cf579 completed April 14, 2026, 7:02 p.m.
Created at: April 10, 2026, 1:30 a.m.