Triple

T30152257
Position Surface form Disambiguated ID Type / Status
Subject WHOIS protocol E766425 entity
Predicate previouslyDefinedInRFC P33255 FINISHED
Object RFC 954
RFC 954 is an early Internet standards document that specifies the original WHOIS protocol used for querying domain and network registration information.
 E1902121 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 954 | Statement: [WHOIS protocol, previouslyDefinedInRFC, RFC 954]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 954
Triple: [WHOIS protocol, previouslyDefinedInRFC, RFC 954]
Generated description
RFC 954 is an early Internet standards document that specifies the original WHOIS protocol used for querying domain and network registration information.
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: previouslyDefinedInRFC
Context triple: [WHOIS protocol, previouslyDefinedInRFC, RFC 954]
  • A. deprecatedInRFC
    Indicates that a specification, feature, or practice has been formally marked as deprecated within a particular RFC document.
  • B. previouslyDefinedIn chosen
    Indicates that something has been defined or introduced earlier in time or in a prior context relative to the current reference point.
  • C. originalRfc
    Indicates that something is the initial or authoritative RFC (Request for Comments) document from which a specification, standard, or later revision originates.
  • D. hasRFC
    Indicates that an entity is associated with, described by, or defined in a specific RFC (Request for Comments) document.
  • E. accountingDefinedInRFC
    Indicates that the accounting mechanism or specification is formally defined or described within a particular RFC (Request for Comments) document.
  • F. None of above.

Provenance (6 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_69f22479cd088190ab4c6f3fce39d1c5 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fdb31800508190beec15adb9bbd292 completed May 8, 2026, 9:55 a.m.
NED1 Entity disambiguation (via context triple) batch_6a274cc0c6a88190b24dcd0e77ca5355 completed June 8, 2026, 11:14 p.m.
NEDg Description generation batch_6a274ddf8d688190b480d115456651c3 completed June 8, 2026, 11:18 p.m.
NED2 Entity disambiguation (via description) batch_6a274eb19fd48190a2d38ace0cc22b77 completed June 8, 2026, 11:22 p.m.
PD Predicate disambiguation batch_69fdb19c381c8190bafb2f565da097f1 completed May 8, 2026, 9:49 a.m.
Created at: April 29, 2026, 7:20 p.m.