Triple

T17559421
Position Surface form Disambiguated ID Type / Status
Subject Fast Application Notification E427660 entity
Predicate relatedTo P37 FINISHED
Object Fast Connection Failover — NE NERFINISHED

How this triple was built (3 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: Fast Connection Failover | Statement: [Fast Application Notification, relatedTo, Fast Connection Failover]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Fast Connection Failover
Context triple: [Fast Application Notification, relatedTo, Fast Connection Failover]
  • A. Timeout Detection and Recovery
    Timeout Detection and Recovery is a Windows graphics subsystem mechanism that monitors GPU responsiveness and automatically resets the graphics driver to prevent system hangs or crashes.
  • B. FastTrack protocol
    The FastTrack protocol is a peer-to-peer file-sharing protocol best known for powering early 2000s services like Kazaa, Grokster, and iMesh.
  • C. Connectivity Fault Management
    Connectivity Fault Management is a standardized Ethernet operations, administration, and maintenance (OAM) framework for detecting, isolating, and managing connectivity issues in carrier and enterprise networks.
  • D. HALDB (High Availability Large Databases)
    HALDB (High Availability Large Databases) is an IMS database organization designed to provide high availability and scalability for very large data volumes through partitioning and online management capabilities.
  • E. Fibre Channel over IP
    Fibre Channel over IP is a storage networking technology that encapsulates Fibre Channel frames within IP packets to enable long-distance connectivity between Fibre Channel SANs over IP networks.
  • 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: Fast Connection Failover
Target entity description: Fast Connection Failover is an Oracle database high-availability feature that enables client applications to rapidly detect and recover from database instance or service failures with minimal disruption.
  • A. Timeout Detection and Recovery
    Timeout Detection and Recovery is a Windows graphics subsystem mechanism that monitors GPU responsiveness and automatically resets the graphics driver to prevent system hangs or crashes.
  • B. FastTrack protocol
    The FastTrack protocol is a peer-to-peer file-sharing protocol best known for powering early 2000s services like Kazaa, Grokster, and iMesh.
  • C. Connectivity Fault Management
    Connectivity Fault Management is a standardized Ethernet operations, administration, and maintenance (OAM) framework for detecting, isolating, and managing connectivity issues in carrier and enterprise networks.
  • D. HALDB (High Availability Large Databases)
    HALDB (High Availability Large Databases) is an IMS database organization designed to provide high availability and scalability for very large data volumes through partitioning and online management capabilities.
  • E. Fibre Channel over IP
    Fibre Channel over IP is a storage networking technology that encapsulates Fibre Channel frames within IP packets to enable long-distance connectivity between Fibre Channel SANs over IP networks.
  • F. None of above. chosen

Provenance (2 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_69d889e0385081908a04b66f4dd4bd0d completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4562573e48190a19f30fe915a5455 completed April 19, 2026, 4:12 a.m.
Created at: April 10, 2026, 5:50 a.m.