Triple

T9346533
Position Surface form Disambiguated ID Type / Status
Subject RFC 1457 E224902 entity
Predicate supersededInContextOf P101 FINISHED
Object later SNMPv2 and SNMPv3 security RFCs LITERAL 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: later SNMPv2 and SNMPv3 security RFCs | Statement: [RFC 1457, supersededInContextOf, later SNMPv2 and SNMPv3 security RFCs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supersededInContextOf
Context triple: [RFC 1457, supersededInContextOf, later SNMPv2 and SNMPv3 security RFCs]
  • A. wasSupersededBy chosen
    Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
  • B. supersededInPrecisionBy
    Indicates that one entity’s level of precision has been replaced or overtaken by another entity’s greater precision.
  • C. supersededSpecificationIn
    Indicates that one specification has been replaced or made obsolete by another specification within a given context or system.
  • D. supersededInCentury
    Indicates that one entity has been replaced or rendered obsolete by another during a specified century.
  • E. emergedInContext
    Indicates that something came into existence, became apparent, or developed within a specific situation, environment, or set of circumstances.
  • F. None of above.

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_69ca842993248190a79ab06968994b86 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd4f0e2ccc8190a68f1c96c0886660 completed April 1, 2026, 4:59 p.m.
PD Predicate disambiguation batch_69cc7a66aef08190b8d668cff5b04f5f completed April 1, 2026, 1:52 a.m.
Created at: March 30, 2026, 7:41 p.m.