Triple
T4596186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Research Cambridge |
E100209
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Microsoft research lab |
C17276
|
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: Microsoft research lab Context triple: [Microsoft Research Cambridge, instanceOf, Microsoft research lab]
-
A.
Microsoft subsidiary
A Microsoft subsidiary is a legally distinct company that is owned or controlled by Microsoft Corporation and operates under its strategic direction while maintaining its own corporate identity.
-
B.
MIT organization
An MIT organization is a structured group within or affiliated with the Massachusetts Institute of Technology that coordinates people, resources, and activities to pursue specific academic, research, professional, or community-focused goals.
-
C.
MIT facility
An MIT facility is a physical or virtual resource, such as a building, laboratory, or specialized space, owned or operated by the Massachusetts Institute of Technology to support its educational, research, and community activities.
-
D.
laboratory at Stanford University
A laboratory at Stanford University is a specialized research facility where faculty, students, and collaborators conduct experiments, develop technologies, and advance knowledge in a particular scientific or engineering discipline.
-
E.
research consortium
A research consortium is a collaborative alliance of multiple organizations or institutions that pool resources, expertise, and infrastructure to conduct joint research toward shared scientific or technological goals.
- F. None of above. chosen
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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:11 p.m.