Triple

T489112
Position Surface form Disambiguated ID Type / Status
Subject IEEE 802.1Qdl TSN for fronthaul standard E9945 entity
Predicate typeOfTraffic P621 FINISHED
Object time-critical fronthaul traffic 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-critical fronthaul traffic | Statement: [IEEE 802.1Qdl TSN for fronthaul standard, typeOfTraffic, time-critical fronthaul traffic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfTraffic
Context triple: [IEEE 802.1Qdl TSN for fronthaul standard, typeOfTraffic, time-critical fronthaul traffic]
  • A. trafficType chosen
    Indicates the category or nature of traffic involved in a given interaction, flow, or connection (e.g., type of network, data, or transport traffic).
  • B. trafficDirection
    Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
  • C. originalTrafficType
    Indicates the initial category or source classification of traffic before any changes, redirects, or reattributions occur.
  • D. trafficLevel
    Indicates the degree of congestion or flow intensity present in a transportation network or route at a given time.
  • E. annualTraffic
    Indicates the typical amount or volume of traffic associated with something over the course of a year.
  • 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_69a2e802e2908190ab17c9479e0b6412 completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2f0e0a9648190b6a3b2da3a3b51e6 completed Feb. 28, 2026, 1:42 p.m.
PD Predicate disambiguation batch_69a2edf63fbc819090ea6ca11f39116a completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.