Triple

T35627618
Position Surface form Disambiguated ID Type / Status
Subject Controller Area Network E1029497 entity
Predicate physicalLayerSpecifiedBy P41113 FINISHED
Object ISO 11898-2 NE NERFINISHED

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: ISO 11898-2 | Statement: [Controller Area Network, physicalLayerSpecifiedBy, ISO 11898-2]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: physicalLayerSpecifiedBy
Context triple: [Controller Area Network, physicalLayerSpecifiedBy, ISO 11898-2]
  • A. physicalLayer
    Indicates a relationship where one entity functions as or pertains to the lowest (physical) layer in a layered system or communication stack, handling the actual transmission of signals or raw data.
  • B. physicalLayerDesignation chosen
    Indicates that one entity specifies or assigns the physical-layer characteristics or identifier used by another entity in a communication system.
  • C. usesPhysicalLayerSimilarTo
    Indicates that one entity employs a physical layer that is similar in structure, technology, or operational characteristics to that used by another entity.
  • D. protocolLayer
    Indicates a relationship where a communication protocol operates at, or is associated with, a specific layer in a protocol stack or network architecture.
  • E. usesPhysicalLayerPipe
    Indicates that one entity employs a specific physical-layer transmission path or channel provided by another entity to carry its data.
  • 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_69f76e07bb0c8190968ea2d836fc42c9 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79f15e6ac8190916822e28724534a completed May 3, 2026, 7:16 p.m.
PD Predicate disambiguation batch_69f79e4bdbcc8190be7a0d2cf8a77b64 completed May 3, 2026, 7:13 p.m.
Created at: May 3, 2026, 4:05 p.m.