Triple
T32709851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CORBA naming service |
E836368
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | distributed directory service |
C59423
|
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: distributed directory service Context triple: [CORBA naming service, instanceOf, distributed directory service]
-
A.
distributed system
A distributed system is a collection of independent computers that appear to users as a single coherent system by coordinating and communicating over a network to achieve common goals.
-
B.
distributed operating system
A distributed operating system is software that manages a collection of independent networked computers and presents them to users and applications as a single coherent system.
-
C.
directory services standard
chosen
A directory services standard defines common protocols, schemas, and interfaces for organizing, storing, and accessing networked identity and resource information in a consistent, interoperable way.
-
D.
distributed file system
A distributed file system is a storage system that manages and presents files across multiple networked machines as a single, unified file hierarchy, providing location transparency, fault tolerance, and scalable access to data.
-
E.
distributed cache
A distributed cache is a system that stores frequently accessed data across multiple networked servers or nodes to improve performance, scalability, and fault tolerance in distributed applications.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:10 a.m.