Triple

T27583571

Position	Surface form	Disambiguated ID	Type / Status
Subject	DDS	`E699637`	entity
Predicate	wireProtocolFullName	`P37668`	FINISHED
Object	Real-Time Publish-Subscribe Protocol Real-Time Publish-Subscribe Protocol is a communication protocol used by the Data Distribution Service (DDS) standard to enable scalable, low-latency, real-time data exchange in distributed systems.	`E1779642`	NE FINISHED

How this triple was built (3 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: Real-Time Publish-Subscribe Protocol | Statement: [DDS, wireProtocolFullName, Real-Time Publish-Subscribe Protocol]

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: Real-Time Publish-Subscribe Protocol
Triple: [DDS, wireProtocolFullName, Real-Time Publish-Subscribe Protocol]

Generated description

Real-Time Publish-Subscribe Protocol is a communication protocol used by the Data Distribution Service (DDS) standard to enable scalable, low-latency, real-time data exchange in distributed systems.

PD Predicate disambiguation gpt-5-mini-2025-08-07

Target predicate: wireProtocolFullName
Context triple: [DDS, wireProtocolFullName, Real-Time Publish-Subscribe Protocol]

A. protocolFullName chosen
Indicates that one entity is the complete, human-readable name of a protocol associated with another entity.
B. protocolName
Indicates the specific communication or interaction protocol used or associated with an entity or connection.
C. networkProtocolDomain
Indicates the network protocol or protocol family within which a given communication, service, or interaction operates.
D. protocolNumber
Indicates the specific identifying number assigned to a protocol that governs or documents an interaction, process, or agreement between entities.
E. protocolIdentifierFormat
Indicates how a protocol’s identifier is structured or formatted.
F. None of above.

Provenance (6 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_69ef6a4cb8b881909b3a8d630fd89df2`	completed	April 27, 2026, 1:53 p.m.
NER	Named-entity recognition	`batch_69f63017bbfc81908e0058e1b6afe3a1`	completed	May 2, 2026, 5:10 p.m.
NED1	Entity disambiguation (via context triple)	`batch_6a12d0d7aa508190a812d773ae6130fb`	completed	May 24, 2026, 10:20 a.m.
NEDg	Description generation	`batch_6a12d1a671948190add200d3ab2db641`	completed	May 24, 2026, 10:23 a.m.
NED2	Entity disambiguation (via description)	`batch_6a12d270e0dc81909c04761a32c1e652`	completed	May 24, 2026, 10:26 a.m.
PD	Predicate disambiguation	`batch_69f62c1921008190a62675a31f66a875`	completed	May 2, 2026, 4:53 p.m.

Created at: April 27, 2026, 2:03 p.m.