Triple

T5480591
Position Surface form Disambiguated ID Type / Status
Subject BGCF E123456 entity
Predicate supportsInterconnect P18380 FINISHED
Object inter-operator PSTN breakout 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: inter-operator PSTN breakout | Statement: [BGCF, supportsInterconnect, inter-operator PSTN breakout]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsInterconnect
Context triple: [BGCF, supportsInterconnect, inter-operator PSTN breakout]
  • A. supportedIn
    Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
  • B. supportsOperationsIn
    Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
  • C. supportsProduct chosen
    Indicates that one entity provides assistance, compatibility, or necessary resources for the operation, use, or maintenance of a specified product.
  • D. supportsNetworkingModel
    Indicates that one entity provides compatibility with, or implementation of, a specified networking model for another entity.
  • E. supportedAs
    Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation 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_69bd4648883481909e9775d43300c5fa completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd93e5d0f08190a6cc9fc408b7c5bb completed March 20, 2026, 6:37 p.m.
PD Predicate disambiguation batch_69bd91a73b148190a865243536a4fe76 completed March 20, 2026, 6:27 p.m.
Created at: March 20, 2026, 2:09 p.m.