Triple

T31970841
Position Surface form Disambiguated ID Type / Status
Subject RFC 1548 E816307 entity
Predicate networkLayerSupport P176046 FINISHED
Object Internet Protocol NE NERFINISHED

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: Internet Protocol | Statement: [RFC 1548, networkLayerSupport, Internet Protocol]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: networkLayerSupport
Context triple: [RFC 1548, networkLayerSupport, Internet Protocol]
  • A. networkLayerIndependence
    Indicates that the relationship or action remains valid and unaffected regardless of the underlying network layer or transport mechanism used.
  • B. networkStack
    Indicates a relationship where one component or layer is part of, or operates within, a structured hierarchy of networking layers (a network stack) to enable communication.
  • C. networkSuite
    Indicates that an entity is part of, provided by, or associated with a particular network-related software or service suite.
  • D. networkLevel
    Indicates the hierarchical position or tier an entity occupies within a network structure.
  • E. linkLayer
    Indicates a relationship where one entity is connected to another at the data link (Layer 2) level of a network stack, enabling direct frame-level communication between them.
  • F. None of above. chosen

Provenance (4 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_69f348f5ae5481909da0247869f51955 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6db6af1d88190989810182354d60f completed May 3, 2026, 5:21 a.m.
PD Predicate disambiguation batch_69f6d82d068c8190940a3200ed760e38 completed May 3, 2026, 5:07 a.m.
PDg Predicate description generation batch_69f6db6a38d881909ecc75cc527910f2 completed May 3, 2026, 5:21 a.m.
Created at: May 1, 2026, 12:10 a.m.