Triple

T12524560
Position Surface form Disambiguated ID Type / Status
Subject Ericsson Cloud Core E299401 entity
Predicate useDomain P1248 FINISHED
Object mobile core 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: mobile core networks | Statement: [Ericsson Cloud Core, useDomain, mobile core networks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: useDomain
Context triple: [Ericsson Cloud Core, useDomain, mobile core networks]
  • A. usedInDomain chosen
    Indicates that something (such as a concept, method, or resource) is applied or utilized within a particular domain or field.
  • B. publicDomain
    Indicates that a work or resource is not protected by intellectual property rights and is freely available for anyone to use, copy, modify, and distribute without restriction.
  • C. defaultDomain
    Indicates that one entity serves as the standard or primary domain associated with another entity, used when no more specific domain is specified.
  • D. inputDomain
    Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
  • E. indicatesDomain
    Indicates a domain or area of knowledge, activity, or applicability to which something (such as a concept, resource, or entity) belongs or is relevant.
  • 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_69d6ada5cdd48190860d9ce30aff69be completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d95f5507b481908d13cc317b7402f6 completed April 10, 2026, 8:36 p.m.
PD Predicate disambiguation batch_69d9540d7b788190a0d57b098e90e491 completed April 10, 2026, 7:48 p.m.
Created at: April 8, 2026, 9:57 p.m.