Triple
T29030670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBP Lookup |
E737718
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Name Binding Protocol operation |
C27294
|
CONCEPT 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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Name Binding Protocol operation Context triple: [NBP Lookup, instanceOf, Name Binding Protocol operation]
-
A.
naming and directory service API
chosen
A naming and directory service API provides standardized operations for registering, looking up, and managing named resources and their associated attributes within a hierarchical or distributed directory.
-
B.
network management protocol
A network management protocol is a standardized set of rules and procedures that enables monitoring, configuring, and controlling devices and services within a computer network.
-
C.
given name bearer
A given name bearer is an individual or entity that holds and is identified by a specific personal name assigned to distinguish them from others.
-
D.
network protocol profile
A network protocol profile is a structured specification that defines how a particular protocol or set of protocols should be configured, constrained, and used to meet specific interoperability, performance, or security requirements in a given context.
-
E.
protocol service
A protocol service is a system component that implements, manages, and coordinates communication rules and message exchanges between distributed entities according to a defined protocol specification.
- F. None of above.
Provenance (1 batch)
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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 9:55 a.m.