Triple

T9865300
Position Surface form Disambiguated ID Type / Status
Subject RFC 4517 E239816 entity
Predicate relatedTo P37 FINISHED
Object RFC 4516 E233825 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 4516 | Statement: [RFC 4517, relatedTo, RFC 4516]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 4516
Context triple: [RFC 4517, relatedTo, RFC 4516]
  • A. RFC 4516 chosen
    RFC 4516 is an Internet standard that specifies the LDAP (Lightweight Directory Access Protocol) Uniform Resource Locator (URL) format used to locate and access directory entries over a network.
  • B. RFC 3416
    RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
  • C. RFC 2156
    RFC 2156 is an Internet standards document that specifies the mapping between X.400 and RFC 822 (Internet) mail systems, updating and replacing earlier guidance on email interoperability.
  • D. RFC 4555
    RFC 4555 is an Internet Engineering Task Force (IETF) specification that defines the MOBIKE (IKEv2 Mobility and Multihoming) protocol extensions for the IKEv2 key management protocol.
  • E. RFC 6145
    RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
  • 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_69ca84e7506c819095cbde4ff16512bb completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb3ba7f288190a15ebec2cc3112c4 completed April 2, 2026, 12:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1eadd95ac81909a265db37b648df0 completed April 5, 2026, 4:53 a.m.
Created at: March 30, 2026, 8:36 p.m.