Triple
T7939380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Borg |
E184354
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internal Google infrastructure system |
C4097
|
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: internal Google infrastructure system Context triple: [Google Borg, instanceOf, internal Google infrastructure system]
-
A.
organizational unit at Google
An organizational unit at Google is a logical grouping of users, devices, and resources within the company’s directory structure used to apply and manage specific policies, settings, and access controls.
-
B.
Google employee
A Google employee is an individual hired by Google to contribute to the development, operation, or support of the company’s products, services, and internal functions within its organizational structure.
-
C.
Google service
chosen
A Google service is any software application or platform provided by Google that delivers specific online functionality—such as search, email, storage, or productivity tools—over the internet to users.
-
D.
Google office
A Google office is a modern, collaborative workspace designed by Google that combines advanced technology, flexible work areas, and employee-focused amenities to foster innovation and productivity.
-
E.
external system
An external system is any independent software or hardware component outside the primary system boundary that interacts with it through defined interfaces to exchange data or services.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:08 p.m.