Triple

T18294113
Position Surface form Disambiguated ID Type / Status
Subject Frame Relay E438186 entity
Predicate encapsulationDefinedIn P23699 FINISHED
Object RFC 1490 NE NERFINISHED

How this triple was built (4 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 1490 | Statement: [Frame Relay, encapsulationDefinedIn, RFC 1490]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 1490
Context triple: [Frame Relay, encapsulationDefinedIn, RFC 1490]
  • A. RFC 1497
    RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
  • B. RFC 1452
    RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
  • C. RFC 1449
    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.
  • D. 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.
  • E. RFC 1349
    RFC 1349 is an older Internet standard that originally defined the Type of Service (TOS) field in the IPv4 header before being superseded by later quality-of-service specifications.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 1490
Target entity description: RFC 1490 is an Internet Engineering Task Force (IETF) standard that specifies how multiple network layer protocols are encapsulated and transported over Frame Relay networks.
  • A. RFC 1497
    RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
  • B. RFC 1452
    RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
  • C. RFC 1449
    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.
  • D. 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.
  • E. RFC 1349
    RFC 1349 is an older Internet standard that originally defined the Type of Service (TOS) field in the IPv4 header before being superseded by later quality-of-service specifications.
  • F. None of above. chosen
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: encapsulationDefinedIn
Context triple: [Frame Relay, encapsulationDefinedIn, RFC 1490]
  • A. encapsulation
    Indicates that one entity encloses, contains, or wraps another entity or set of details within a defined boundary, often hiding internal structure from external access.
  • B. areDefinedIn chosen
    Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
  • C. alsoDefinedInPackage
    Indicates that the same element or concept is additionally defined or declared in another software package.
  • D. encapsulatesValue
    Indicates that one entity contains and represents the underlying value of another entity as its internal content.
  • E. definedVia
    Indicates that one entity is specified, characterized, or given its meaning by reference to another entity or construct.
  • 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_69d8b915e3e881909125d760c15d0c29 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e5010205bc8190a32fe731ead3d988 completed April 19, 2026, 4:21 p.m.
PD Predicate disambiguation batch_69e44fdf43d08190bbcfb6b1fe3cc0ee completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:35 a.m.