Triple
T22649804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meta Open Source team |
E559062
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational unit at Meta |
C39574
|
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: organizational unit at Meta Context triple: [Meta Open Source team, instanceOf, organizational unit at Meta]
-
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.
organizational unit of Microsoft
An organizational unit of Microsoft is a logical container within a directory service used to group and manage users, computers, and other resources under common administrative policies and controls.
-
C.
Meta Platforms facility
A Meta Platforms facility is a physical site owned or operated by Meta (formerly Facebook) that houses its offices, data centers, research labs, or other infrastructure supporting the company’s products and services.
-
D.
organizational unit category
An organizational unit category is a classification that groups organizational units based on shared characteristics such as function, structure, or hierarchy to support consistent management and analysis.
-
E.
organizational unit designation
chosen
An organizational unit designation is a label or identifier that specifies a distinct division, department, or functional group within an organization’s structure.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:05 p.m.