Triple

T13101762
Position Surface form Disambiguated ID Type / Status
Subject IEEE 802.1DP E310734 entity
Predicate relatedTo P37 FINISHED
Object IEEE 802.1Qbu E57122 NE 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: IEEE 802.1Qbu | Statement: [IEEE 802.1DP, relatedTo, IEEE 802.1Qbu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IEEE 802.1Qbu
Context triple: [IEEE 802.1DP, relatedTo, IEEE 802.1Qbu]
  • A. IEEE 802.1Qbu chosen
    IEEE 802.1Qbu is an Ethernet networking standard that defines frame preemption to improve latency and reliability for time-sensitive traffic in bridged networks.
  • B. IEEE 802.1Qbb
    IEEE 802.1Qbb is an Ethernet networking standard that defines Priority-based Flow Control (PFC) to enable lossless transmission for selected traffic classes in data center and converged network environments.
  • C. IEEE 802.1Qbh
    IEEE 802.1Qbh is an Ethernet networking standard that defines bridge port extension mechanisms to support virtualized and distributed switching environments.
  • D. IEEE 802.1Qau
    IEEE 802.1Qau is an Ethernet networking standard that defines congestion notification mechanisms to improve traffic management and prevent packet loss in data center and carrier networks.
  • E. IEEE 802.1Qej
    IEEE 802.1Qej is an amendment to the IEEE 802.1Q standard that enhances bridged network capabilities, particularly for improved traffic management and time-sensitive networking applications.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d806a872d08190a329806f8ff30df4 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d981515d488190908d3cca1b84a42d completed April 10, 2026, 11:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69f70a227d2c81908da0089d0e0387c6 completed May 3, 2026, 8:41 a.m.
Created at: April 9, 2026, 9:04 p.m.