Triple

T21224993
Position Surface form Disambiguated ID Type / Status
Subject Session Initiation Protocol E523064 entity
Predicate supportsReliabilityExtension P10377 FINISHED
Object PRACK 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: PRACK | Statement: [Session Initiation Protocol, supportsReliabilityExtension, PRACK]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsReliabilityExtension
Context triple: [Session Initiation Protocol, supportsReliabilityExtension, PRACK]
  • A. supportsRelayAgents
    Indicates that one entity is capable of working with or providing functionality for relay agents that forward or mediate communications between other entities.
  • B. reliabilityRecord
    Indicates that there exists a record or documentation capturing the reliability characteristics, performance, or history associated with an entity or relationship.
  • C. reliabilityMechanism chosen
    Indicates a mechanism or process that ensures the dependable, consistent, and correct functioning of a system or relationship.
  • D. hasReliabilityGoal
    Indicates that an entity is associated with or assigned a specific reliability-related objective or target.
  • E. reliabilityCharacteristic
    Indicates that one entity specifies or embodies a reliability-related property, feature, or performance attribute of another entity.
  • 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_69e0b512ad94819087942b2ed925185f completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e734aa82c4819086cef6364619b4e9 completed April 21, 2026, 8:26 a.m.
PD Predicate disambiguation batch_69e5f60e1a888190ba75e2e900270a4e completed April 20, 2026, 9:46 a.m.
Created at: April 16, 2026, 3:44 p.m.