Triple

T11502610
Position Surface form Disambiguated ID Type / Status
Subject SMTP Service Extension for Secure SMTP over Transport Layer Security E272699 entity
Predicate definedIn P775 FINISHED
Object RFC 3207 E52728 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 3207 | Statement: [SMTP Service Extension for Secure SMTP over Transport Layer Security, definedIn, RFC 3207]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 3207
Context triple: [SMTP Service Extension for Secure SMTP over Transport Layer Security, definedIn, RFC 3207]
  • A. RFC 3207 chosen
    RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
  • B. RFC 3377
    RFC 3377 is an Internet Engineering Task Force (IETF) document that previously specified Lightweight Directory Access Protocol (LDAP) version 3 technical details before being superseded by later standards.
  • C. RFC 3727
    RFC 3727 is an Internet Engineering Task Force (IETF) document that defined earlier specifications for LDAP-related schema or matching rules, later superseded by RFC 4517.
  • D. RFC 3205
    RFC 3205 is an informational Internet standard that provides guidelines and considerations for designing and deploying application protocols that use HTTP as a substrate.
  • E. RFC 3710
    RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
  • 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_69d6aae2c3748190bed2ea50dfb160dc completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d85de55cbc8190be71c2d03dc044f2 completed April 10, 2026, 2:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69e624d666c081908253cea4e2da1a4a completed April 20, 2026, 1:06 p.m.
Created at: April 8, 2026, 9:36 p.m.