Triple

T3705202
Position Surface form Disambiguated ID Type / Status
Subject IEEE 802.3 Clause 28 E80873 entity
Predicate referenceInPractice P17905 FINISHED
Object “Clause 28 Auto-Negotiation” in Ethernet specifications 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: “Clause 28 Auto-Negotiation” in Ethernet specifications | Statement: [IEEE 802.3 Clause 28, referenceInPractice, “Clause 28 Auto-Negotiation” in Ethernet specifications]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: referenceInPractice
Context triple: [IEEE 802.3 Clause 28, referenceInPractice, “Clause 28 Auto-Negotiation” in Ethernet specifications]
  • A. articleReference chosen
    Indicates that one entity cites, mentions, or refers to another entity within an article or written document.
  • B. usedInPractice
    Indicates that something is actually applied or implemented in real-world practice rather than just being theoretical or proposed.
  • C. referencePolicy
    Indicates that one entity defines rules or guidelines governing how another entity may be referred to, cited, or mentioned.
  • D. referenceClient
    Indicates that one entity serves as a client reference for another, typically used to validate or endorse the second entity’s services or capabilities.
  • E. primaryReference
    Indicates that one entity serves as the main or authoritative source of information or citation for another entity.
  • 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_69ad8b1793888190a5f70e4b21dc05a1 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adc54bbfcc8190bec9c16e3749c3b1 completed March 8, 2026, 6:51 p.m.
PD Predicate disambiguation batch_69adc041a8608190a2d543dab6d2ef6c completed March 8, 2026, 6:30 p.m.
Created at: March 8, 2026, 3:33 p.m.