Triple
T27583571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDS |
E699637
|
entity |
| Predicate | wireProtocolFullName |
P37668
|
FINISHED |
| Object | Real-Time Publish-Subscribe Protocol |
—
|
NE NERFINISHED |
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: Real-Time Publish-Subscribe Protocol | Statement: [DDS, wireProtocolFullName, Real-Time Publish-Subscribe Protocol]
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 (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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63017bbfc81908e0058e1b6afe3a1 |
completed | May 2, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:03 p.m.