Triple

T10329101
Position Surface form Disambiguated ID Type / Status
Subject IANA media type registry E242832 entity
Predicate documentedIn P309 FINISHED
Object RFC 2046 E832817 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 2046 | Statement: [IANA media type registry, documentedIn, RFC 2046]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 2046
Context triple: [IANA media type registry, documentedIn, RFC 2046]
  • A. RFC 2046 chosen
    RFC 2046 is an Internet standard that defines the structure and types of media content used in the Multipurpose Internet Mail Extensions (MIME) framework.
  • B. RFC 2045
    RFC 2045 is an Internet standard that defines the format and encoding rules for MIME message bodies used in email and related Internet protocols.
  • C. RFC 2049
    RFC 2049 is an Internet standards document that defines the conformance, operational considerations, and security issues for the MIME (Multipurpose Internet Mail Extensions) specification used in Internet email.
  • D. RFC 1022
    RFC 1022 is an early Internet standards document that was later superseded by RFC 1122, which more comprehensively defines host requirements for Internet protocols.
  • E. MIME
    MIME (Multipurpose Internet Mail Extensions) is an internet standard that extends the format of email to support text in character sets beyond ASCII, as well as attachments like images, audio, video, and application files.
  • 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_69d381af787481908bc401325c760a88 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d7cfd54c8190b6f88598339536d1 completed April 7, 2026, 10:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69d71db4a8dc81909adb2a044e74fd6b completed April 9, 2026, 3:32 a.m.
Created at: April 6, 2026, 11:52 a.m.