Triple

T9029783
Position Surface form Disambiguated ID Type / Status
Subject G.fast E216138 entity
Predicate usesDuplexMethod P85772 FINISHED
Object time-division duplexing 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: time-division duplexing | Statement: [G.fast, usesDuplexMethod, time-division duplexing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesDuplexMethod
Context triple: [G.fast, usesDuplexMethod, time-division duplexing]
  • A. duplexModeInOriginalSpec
    Indicates that the duplex (two-sided operation) mode is defined according to the original specification.
  • B. duplexMode
    Indicates whether a communication link or device operates in half-duplex or full-duplex mode, defining if data can flow in one or both directions simultaneously.
  • C. laterSupportedDuplexMode
    Indicates that one entity provided support for duplex mode at a later time than another entity.
  • D. usesPairsForTransmit
    Indicates that an entity performs transmission by utilizing paired elements (such as wires, channels, or signals) as the medium or mechanism for sending information or energy.
  • E. usesPairsForReceive
    Indicates that an entity performs its receiving operation by using paired elements or resources as the basis for that reception.
  • 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_69ca83a5fa88819088144801b4dd7245 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6a9bcb508190b58751f1772407d4 completed April 1, 2026, 12:45 a.m.
PD Predicate disambiguation batch_69cc5ee3597c81908919cf866ae95c24 completed March 31, 2026, 11:55 p.m.
PDg Predicate description generation batch_69cc5f6dec4081909379bd57c02a5710 completed March 31, 2026, 11:57 p.m.
Created at: March 30, 2026, 7:08 p.m.