Triple

T3622276
Position Surface form Disambiguated ID Type / Status
Subject IEEE 802.1Qfe E76753 entity
Predicate hasAbbreviation P43 FINISHED
Object 802.1Qfe E76753 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: 802.1Qfe | Statement: [IEEE 802.1Qfe, hasAbbreviation, 802.1Qfe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 802.1Qfe
Context triple: [IEEE 802.1Qfe, hasAbbreviation, 802.1Qfe]
  • A. IEEE 802.1Qfe chosen
    IEEE 802.1Qfe is a specific amendment within the IEEE 802.1 family that defines enhancements to Ethernet bridging and related network management functions.
  • B. 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.
  • C. IEEE 802.1Qfg
    IEEE 802.1Qfg is an Ethernet networking standard within the IEEE 802.1 family that defines mechanisms for enhanced reliability and fault tolerance in bridged networks.
  • D. IEEE 802.1Qfr
    IEEE 802.1Qfr is an Ethernet networking standard within the IEEE 802.1 family that specifies mechanisms for enhanced reliability and performance in time-sensitive and deterministic networks.
  • E. IEEE 802.1Qfc
    IEEE 802.1Qfc is an amendment to the IEEE 802.1Q standard that specifies enhancements for frame preemption and traffic scheduling in Time-Sensitive Networking (TSN) 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_69ad85dae2fc81908d1ceadbc6af0089 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc2bb12cc8190bd67597cf3b66a3a completed March 8, 2026, 6:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69b43320955c8190910c0f15c80f41f4 completed March 13, 2026, 3:54 p.m.
Created at: March 8, 2026, 3:23 p.m.