Triple

T2724437
Position Surface form Disambiguated ID Type / Status
Subject STD 5 E60157 entity
Predicate primarySpecification P41883 FINISHED
Object RFC 791 E9801 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: RFC 791 | Statement: [STD 5, primarySpecification, RFC 791]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 791
Context triple: [STD 5, primarySpecification, RFC 791]
  • A. RFC 791 chosen
    RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
  • B. RFC 792
    RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
  • C. RFC 793
    RFC 793 is the foundational Internet standard that defines the Transmission Control Protocol (TCP), specifying how reliable, ordered, and error-checked data transmission works between hosts on an IP network.
  • D. RFC 1449
    RFC 1449 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) used for managing devices on IP networks.
  • E. RFC 974
    RFC 974 is an early Internet standard that defined the original mechanisms for mail routing and the use of MX records in the Domain Name System (DNS).
  • 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: primarySpecification
Context triple: [STD 5, primarySpecification, RFC 791]
  • A. firstSpecified
    Indicates that the subject is the earliest or initial entity explicitly designated or chosen among a set of specified entities.
  • B. primaryType
    Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
  • C. primaryProduct
    Indicates that one entity is the main or most important product associated with, produced by, or offered by another entity.
  • D. primaryCriterion
    Indicates that one factor is designated as the main or most important basis for a decision, judgment, or selection among alternatives.
  • E. primaryComponent
    Indicates that one entity serves as the main or most important component within another entity or system.
  • 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_69ab4b746d248190958e052045c09255 completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdacc0a6881909b64a4d22e1d7690 completed March 7, 2026, 7:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69afc63dfd4c819093599e6e1f55e9f8 completed March 10, 2026, 7:20 a.m.
PD Predicate disambiguation batch_69abd82586f88190a98f60d3247fe2d3 completed March 7, 2026, 7:47 a.m.
PDg Predicate description generation batch_69abd949c120819099a9d56eb71a0339 completed March 7, 2026, 7:52 a.m.
Created at: March 6, 2026, 9:55 p.m.