Triple

T1069804
Position Surface form Disambiguated ID Type / Status
Subject Wi‑Fi CERTIFIED Passpoint E23298 entity
Predicate supportsRoamingWith P23934 FINISHED
Object cellular networks 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: cellular networks | Statement: [Wi‑Fi CERTIFIED Passpoint, supportsRoamingWith, cellular networks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsRoamingWith
Context triple: [Wi‑Fi CERTIFIED Passpoint, supportsRoamingWith, cellular networks]
  • A. supportsFeature
    Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
  • B. supportsRouting
    Indicates that one entity provides the capability to determine and direct paths or routes for another entity’s traffic, requests, or messages.
  • C. supportsRegionRestriction
    Indicates that an entity enforces or accommodates limitations on availability or access based on geographic regions.
  • D. supportsRegion
    Indicates that one entity provides assistance, resources, or backing to a specific geographic or administrative region.
  • E. supportsOperationsIn
    Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
  • 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_69a493ee1f908190992b5f0d1b04459b completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b914b4908190886d6698294c6b5b completed March 1, 2026, 10:09 p.m.
PD Predicate disambiguation batch_69a4b73844708190a16c9e9824ca2fb6 completed March 1, 2026, 10:01 p.m.
PDg Predicate description generation batch_69a4b8d5076481908640a0d873efdf14 completed March 1, 2026, 10:08 p.m.
Created at: March 1, 2026, 7:42 p.m.