Triple

T1917477
Position Surface form Disambiguated ID Type / Status
Subject RFC 1906 E40050 entity
Predicate obsoletes P101 FINISHED
Object RFC 1449 E214653 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 1449 | Statement: [RFC 1906, obsoletes, RFC 1449]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 1449
Context triple: [RFC 1906, obsoletes, RFC 1449]
  • A. RFC 1449 chosen
    RFC 1449 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) used for managing devices on IP networks.
  • B. RFC 1448
    RFC 1448 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) before being superseded by later revisions such as RFC 1905.
  • C. RFC 1446
    RFC 1446 is an early Internet standards document that defined mechanisms for managing network devices using the Simple Network Management Protocol (SNMP) before being superseded by later revisions.
  • D. RFC 1443
    RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
  • E. RFC 1450
    RFC 1450 is an early Internet standards document related to network management that was later superseded by RFC 1901.
  • 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_69a8864298748190a2f2fd34f7ef8d77 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb2107fe48190bafff825f1f805ad completed March 7, 2026, 5:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69af989af058819082c35bee706d0ea0 completed March 10, 2026, 4:05 a.m.
Created at: March 4, 2026, 7:35 p.m.