Triple

T18293139
Position Surface form Disambiguated ID Type / Status
Subject ITU-T Recommendation G.992.1 E438164 entity
Predicate supportsUpstreamRateUpTo P118310 FINISHED
Object 1 Mbit/s 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: 1 Mbit/s | Statement: [ITU-T Recommendation G.992.1, supportsUpstreamRateUpTo, 1 Mbit/s]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsUpstreamRateUpTo
Context triple: [ITU-T Recommendation G.992.1, supportsUpstreamRateUpTo, 1 Mbit/s]
  • A. supportsRateLimiting
    Indicates that one entity provides or is compatible with mechanisms to restrict the rate at which another entity can perform actions or process requests.
  • B. upstreamLimitOf chosen
    Indicates that one entity defines or constrains the maximum upstream capacity, flow, or allowable limit for another entity in a system or process.
  • C. supportsBandwidths
    Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
  • D. supportsCodeRates
    Indicates that one entity is capable of handling, processing, or operating at the specific code rates associated with another entity.
  • E. hasApproximateRate
    Indicates that one entity is associated with another entity representing an estimated or non-exact rate or frequency.
  • 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_69d8b915e3e881909125d760c15d0c29 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e50100d6488190bbe73668df9c4046 completed April 19, 2026, 4:21 p.m.
PD Predicate disambiguation batch_69e44fdf43d08190bbcfb6b1fe3cc0ee completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:35 a.m.