Triple

T571048
Position Surface form Disambiguated ID Type / Status
Subject IEEE 802.1Qds E13663 entity
Predicate relatedTo P37 FINISHED
Object IEEE 802.1Q E93116 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.1Q | Statement: [IEEE 802.1Qds, relatedTo, IEEE 802.1Q]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IEEE 802.1Q
Context triple: [IEEE 802.1Qds, relatedTo, IEEE 802.1Q]
  • A. IEEE 802.1Q series chosen
    The IEEE 802.1Q series is a family of networking standards that define virtual LANs (VLANs) and related bridging, forwarding, and time-sensitive networking mechanisms in Ethernet networks.
  • B. IEEE 802.1Qfe
    IEEE 802.1Qfe is a specific amendment within the IEEE 802.1 family that defines enhancements to Ethernet bridging and related network management functions.
  • C. IEEE 802.1Qel
    IEEE 802.1Qel is an Ethernet networking standard that defines enhancements for scheduled traffic and latency management in time-sensitive networks.
  • D. IEEE 802.1Qex
    IEEE 802.1Qex is an amendment to the IEEE 802.1Q standard that enhances Ethernet bridging by adding advanced features for traffic engineering and improved control of data paths in bridged networks.
  • E. IEEE 802.1Qfa
    IEEE 802.1Qfa is an amendment to the IEEE 802.1Q standard that specifies enhancements for deterministic, time-sensitive networking in bridged Ethernet networks.
  • 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_69a4933fa4d88190a7949cc83c08c5c1 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49b483ac08190b3be152a7cf42011 completed March 1, 2026, 8:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69a7cf473e48819095390a5904429a9c completed March 4, 2026, 6:20 a.m.
Created at: March 1, 2026, 7:33 p.m.