Triple

T10623939
Position Surface form Disambiguated ID Type / Status
Subject IETF Internet standards process E250273 entity
Predicate documentedIn P309 FINISHED
Object RFC 6410 E186437 NE 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: RFC 6410 | Statement: [IETF Internet standards process, documentedIn, RFC 6410]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 6410
Context triple: [IETF Internet standards process, documentedIn, RFC 6410]
  • A. RFC 6410 chosen
    RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
  • B. RFC 6409
    RFC 6409 is an Internet standards document that originally defined the Message Submission protocol for email (port 587), later superseded by RFC 8314.
  • C. RFC 6052
    RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
  • D. RFC 6437
    RFC 6437 is an Internet Engineering Task Force (IETF) specification that originally defined the IPv6 flow label behavior and usage before being superseded by RFC 8999.
  • E. RFC 6840
    RFC 6840 is an Internet Engineering Task Force (IETF) standards document that clarifies, updates, and consolidates the core specifications for the DNS Security Extensions (DNSSEC) protocol suite.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6aa5993448190a493b790b8f85010 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6df7f11fc8190aed858f2e1443c08 completed April 8, 2026, 11:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69d97a356e548190ab7a4a2c7111ba89 completed April 10, 2026, 10:31 p.m.
Created at: April 8, 2026, 8:52 p.m.