Triple

T22830010
Position Surface form Disambiguated ID Type / Status
Subject Multiparty Multimedia Session Control E565770 entity
Predicate documentation P4310 FINISHED
Object RFC 2327 NE NERFINISHED

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 2327 | Statement: [Multiparty Multimedia Session Control, documentation, RFC 2327]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 2327
Context triple: [Multiparty Multimedia Session Control, documentation, RFC 2327]
  • A. RFC 2327 chosen
    RFC 2327 is the original IETF specification that defines the Session Description Protocol (SDP) used to describe multimedia communication sessions for purposes such as session announcement and invitation.
  • B. 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.
  • C. RFC 3207
    RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
  • D. RFC 2787
    RFC 2787 is an Internet Engineering Task Force (IETF) document that originally specified a now-superseded networking standard or protocol later replaced by RFC 4632.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e24585ab1c81909b2b5065d15805d5 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17e2ac8d48190b6dc7edc5ad82bc7 completed April 29, 2026, 3:42 a.m.
Created at: April 17, 2026, 3:34 p.m.