Triple

T21226480
Position Surface form Disambiguated ID Type / Status
Subject Nudm E523095 entity
Predicate supportsRoamingScenarios P143284 FINISHED
Object true 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: true | Statement: [Nudm, supportsRoamingScenarios, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsRoamingScenarios
Context triple: [Nudm, supportsRoamingScenarios, true]
  • A. supportsRoamingWith
    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. supportsTethering
    Indicates that one entity enables or allows another entity to share its network connection with additional devices (i.e., provides tethering capability).
  • C. supportsEsim
    Indicates that one entity provides compatibility with, or the ability to use, an embedded SIM (eSIM) for another entity.
  • D. 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.
  • E. supportsHandoverWith
    Indicates that one entity is capable of transferring control, responsibility, or an ongoing process to another entity in a coordinated handover.
  • 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_69e0b512ad94819087942b2ed925185f completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e734ab3f6c819083e277ea1c33134e completed April 21, 2026, 8:26 a.m.
PD Predicate disambiguation batch_69e5f60e1a888190ba75e2e900270a4e completed April 20, 2026, 9:46 a.m.
PDg Predicate description generation batch_69e5f993240c8190847c0b08e65726c8 completed April 20, 2026, 10:01 a.m.
Created at: April 16, 2026, 3:44 p.m.