Triple

T10316170
Position Surface form Disambiguated ID Type / Status
Subject RFC 3980 E242019 entity
Predicate supersededBySpecification P82887 FINISHED
Object RFC 7143 E48585 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 7143 | Statement: [RFC 3980, supersededBySpecification, RFC 7143]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 7143
Context triple: [RFC 3980, supersededBySpecification, RFC 7143]
  • A. RFC 7143 chosen
    RFC 7143 is the Internet Engineering Task Force (IETF) standard that defines the updated core specification for the iSCSI (Internet Small Computer Systems Interface) protocol used for block-level storage over IP networks.
  • B. RFC 7483
    RFC 7483 is the IETF specification that defines the JSON-based data format and usage for the Registration Data Access Protocol (RDAP) used to query domain and network registration information.
  • C. RFC 7344
    RFC 7344 is an Internet Engineering Task Force (IETF) standard that specifies automated mechanisms for maintaining DNSSEC delegation trust using CDS and related records.
  • D. RFC 7432
    RFC 7432 is an IETF standard that defines Ethernet VPN (EVPN), a BGP-based control plane for multipoint Layer 2 VPN services over IP/MPLS networks.
  • E. RFC 7144
    RFC 7144 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces the original iSCSI protocol specification defined in RFC 3720.
  • 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: supersededBySpecification
Context triple: [RFC 3980, supersededBySpecification, RFC 7143]
  • A. supersededSpecificationIn chosen
    Indicates that one specification has been replaced or made obsolete by another specification within a given context or system.
  • B. wasSupersededBy
    Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
  • C. supersededInPrecisionBy
    Indicates that one entity’s level of precision has been replaced or overtaken by another entity’s greater precision.
  • D. obsoletedStandard
    Indicates that one standard has been rendered obsolete or superseded by another standard.
  • E. isObsoleteFor
    Indicates that something is no longer current, valid, or in use for a particular entity, context, or purpose.
  • F. None of above.

Provenance (4 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_69d381ac38808190a8ca7457c85b625b completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d7ccb7ec8190a538cf279e48116e completed April 7, 2026, 10:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69d75036ed008190aee48695ad7f857d completed April 9, 2026, 7:07 a.m.
PD Predicate disambiguation batch_69d4d1f4f354819080b4ed4bc61bdff6 completed April 7, 2026, 9:44 a.m.
Created at: April 6, 2026, 11:49 a.m.