Triple

T21226610
Position Surface form Disambiguated ID Type / Status
Subject Network Slice Instance E523098 entity
Predicate mayBeDedicatedTo P75386 FINISHED
Object single enterprise customer 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: single enterprise customer | Statement: [Network Slice Instance, mayBeDedicatedTo, single enterprise customer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayBeDedicatedTo
Context triple: [Network Slice Instance, mayBeDedicatedTo, single enterprise customer]
  • A. possibleDedication chosen
    Indicates that one entity is potentially dedicated or devoted to another, but this dedication is uncertain or not definitively established.
  • B. hasDedicationPurpose
    Indicates that something is dedicated, devoted, or assigned to serve a particular purpose or function.
  • C. dedicationStatus
    Indicates the current state or condition of an entity’s dedication or commitment, such as whether it is active, pending, completed, or otherwise defined.
  • D. dedicationType
    Indicates the specific kind or category of dedication that characterizes the relationship or action between entities.
  • E. oftenDedicatedTo
    Indicates that something is frequently or habitually devoted, assigned, or committed to a particular purpose, activity, or recipient.
  • 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_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.
Created at: April 16, 2026, 3:44 p.m.