Triple

T8601184
Position Surface form Disambiguated ID Type / Status
Subject RFC 1907 E203677 entity
Predicate obsoletedStandard P83799 FINISHED
Object STD 62 E200055 NE FINISHED

How this triple was built (3 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: STD 62 | Statement: [RFC 1907, obsoletedStandard, STD 62]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: STD 62
Context triple: [RFC 1907, obsoletedStandard, STD 62]
  • A. STD 62 chosen
    STD 62 is an Internet Standards Track specification that defines part of the Simple Network Management Protocol (SNMP) framework for network management on the Internet.
  • B. STD 68
    STD 68 is an Internet Standard that specifies the core Internet Control Message Protocol (ICMP) used for network diagnostics and error reporting in IP networks.
  • C. STD 5
    STD 5 is the Internet Standard that defines the core Internet Protocol (IP), as specified primarily in RFC 791.
  • D. STD 7
    STD 7 is an Internet Standards Track specification in the IETF standards series, corresponding to RFC 2131, which defines the Dynamic Host Configuration Protocol (DHCP) for automated IP address assignment and configuration.
  • E. STD 1
    STD 1 is an early Internet Standard that specifies the foundational Internet Protocol (IP), defining how data packets are addressed and routed across interconnected networks.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: obsoletedStandard
Context triple: [RFC 1907, obsoletedStandard, STD 62]
  • A. implementedAsStandardBy
    Indicates that a standard is put into practice or realized through implementation by a specific entity (such as an organization, system, or component).
  • B. becameStandardFor
    Indicates that something was adopted and established as the usual or accepted norm for a particular purpose, context, or group.
  • C. eraOfObsolescence
    Indicates the time period during which something becomes outdated, no longer useful, or superseded by newer alternatives.
  • D. firstStandardized
    Indicates that an entity is the earliest or primary instance to which a standard or uniform specification has been first applied among comparable entities.
  • E. firstStandardApproved
    Indicates that an entity is the earliest or initial standard that has received formal approval.
  • F. None of above. chosen

Provenance (5 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_69ca832b56948190ba751cec255308f1 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cc46d8ff408190acc7cd8dc99b2689 completed March 31, 2026, 10:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69cea8f13f7081908317c1b2d87a51b2 completed April 2, 2026, 5:35 p.m.
PD Predicate disambiguation batch_69cc454eb2908190acf0e4336bc67e7b completed March 31, 2026, 10:06 p.m.
PDg Predicate description generation batch_69cc46c330bc8190a9b644078881c6ff completed March 31, 2026, 10:12 p.m.
Created at: March 30, 2026, 6:24 p.m.