Triple

T36643279
Position Surface form Disambiguated ID Type / Status
Subject VID (Virtual Infrastructure Deployment) E904636 entity
Predicate interactsWith P3970 FINISHED
Object ONAP SDN-C
ONAP SDN-C is the Software-Defined Networking Controller component of the ONAP platform, responsible for orchestrating and managing network connectivity and services across programmable networks.
E262484 NE 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: ONAP SDN-C | Statement: [VID (Virtual Infrastructure Deployment), interactsWith, ONAP SDN-C]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: ONAP SDN-C
Triple: [VID (Virtual Infrastructure Deployment), interactsWith, ONAP SDN-C]
Generated description
ONAP SDN-C is the Software-Defined Networking Controller component of the ONAP platform, responsible for orchestrating and managing network connectivity and services across programmable networks.

Provenance (5 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_69f76e6d3a3c81909db73eda9e0516bd completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7c4dd4e2081909db5cc375163d665 completed May 3, 2026, 9:57 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3c171a3dcc8190a3f582d4b13beff2 completed June 24, 2026, 5:42 p.m.
NEDg Description generation batch_6a3c17947b008190accec5b1b3786722 completed June 24, 2026, 5:44 p.m.
NED2 Entity disambiguation (via description) batch_6a3c6b764c188190a0bf2e2db5c67ab8 completed June 24, 2026, 11:42 p.m.
Created at: May 3, 2026, 4:11 p.m.