Triple

T21674324
Position Surface form Disambiguated ID Type / Status
Subject Tele E534928 entity
Predicate hasControlLayout P102036 FINISHED
Object master volume 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: master volume | Statement: [Tele, hasControlLayout, master volume]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasControlLayout
Context triple: [Tele, hasControlLayout, master volume]
  • A. hasControlElement
    Indicates that one entity includes or is associated with a component specifically intended to control, regulate, or influence its behavior or operation.
  • B. hasLayout
    Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another entity.
  • C. hasLayoutElement chosen
    Indicates that one entity includes, contains, or is associated with a specific layout element as part of its structural or visual arrangement.
  • D. hasControlFields
    Indicates that one entity possesses or defines control-related parameters, settings, or fields that govern the behavior or configuration of another entity or process.
  • E. hasNavigationControl
    Indicates that one entity possesses authority or capability to direct, manage, or influence the movement or course of another 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_69e0c46898008190aa618a4af55bd1ee completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef8a0ed5388190b8f1932fb3f11c6a completed April 27, 2026, 4:08 p.m.
PD Predicate disambiguation batch_69e6968abfdc81909cf9e0bd72db9eca completed April 20, 2026, 9:11 p.m.
Created at: April 16, 2026, 6:41 p.m.