Triple
T22445898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dart team |
E554861
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Google team |
C14963
|
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: Google team Context triple: [Dart team, instanceOf, Google team]
-
A.
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.
-
B.
Google X project
A Google X project is an experimental, high-risk, high-reward initiative within Alphabet’s research lab focused on developing breakthrough technologies that could have massive, long-term societal impact.
-
C.
organizational unit at Google
chosen
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.
-
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.
Google developer product
A Google developer product is a tool, platform, or service provided by Google that enables software developers to build, test, deploy, and optimize applications or integrations within the Google ecosystem or on the open web.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:47 p.m.