Triple
T27866356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Distributed Component Object Model |
E704368
|
entity |
| Predicate | originallyUsedProtocol |
P107773
|
FINISHED |
| Object | DCE/RPC over named pipes |
—
|
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: DCE/RPC over named pipes | Statement: [Distributed Component Object Model, originallyUsedProtocol, DCE/RPC over named pipes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyUsedProtocol Context triple: [Distributed Component Object Model, originallyUsedProtocol, DCE/RPC over named pipes]
-
A.
usedInProtocol
Indicates that something (e.g., a method, component, or resource) is employed as part of the steps or structure of a specific protocol.
-
B.
primaryProtocol
chosen
Indicates that one protocol is designated as the main or default protocol used in a given context or interaction.
-
C.
protocolUse
Indicates that an entity employs or relies on a specific protocol to perform a communication, interaction, or operation.
-
D.
negotiatesProtocolUsing
Indicates that one entity establishes or conducts a negotiation process with another entity using a specified protocol as the communication or agreement mechanism.
-
E.
mayUseProtocol
Indicates that an entity is permitted or authorized to employ a specified protocol for communication or operation.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: April 27, 2026, 6:21 p.m.