Triple
T12524553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ericsson Cloud Core |
E299401
|
entity |
| Predicate | supportsFeature |
P203
|
FINISHED |
| Object | multi-vendor interoperability |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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: multi-vendor interoperability | Statement: [Ericsson Cloud Core, supportsFeature, multi-vendor interoperability]
Provenance (2 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_69d9545c2aa081908e8a5a94d30e23eb |
completed | April 10, 2026, 7:49 p.m. |
Created at: April 8, 2026, 9:57 p.m.