Triple

T8472343
Position Surface form Disambiguated ID Type / Status
Subject iDEN E200308 entity
Predicate supportsRoaming P23934 FINISHED
Object intra-network roaming 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: intra-network roaming | Statement: [iDEN, supportsRoaming, intra-network roaming]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsRoaming
Context triple: [iDEN, supportsRoaming, intra-network roaming]
  • A. supportsRoamingWith chosen
    Indicates that one entity enables or is compatible with another entity’s ability to operate or be accessed while roaming across different networks or locations.
  • B. supportsLocation
    Indicates that one entity provides the necessary structure, foundation, or capacity to hold, host, or accommodate another entity at a particular place or position.
  • C. supportsEsim
    Indicates that one entity provides compatibility with, or the ability to use, an embedded SIM (eSIM) for another entity.
  • D. supportsHandoverWith
    Indicates that one entity is capable of transferring control, responsibility, or an ongoing process to another entity in a coordinated handover.
  • E. supportsFeature
    Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
  • 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_69ca831a4f348190bfdd09250e86ae35 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe4f4fbf481909e4fd7c078b27477 completed March 31, 2026, 3:15 p.m.
PD Predicate disambiguation batch_69cbd10072cc819084be1ed9ac7ebe9d completed March 31, 2026, 1:49 p.m.
Created at: March 30, 2026, 6:11 p.m.