Triple
T37754855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM Austin Research Laboratory |
E941084
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IBM research facility |
C23405
|
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: IBM research facility Context triple: [IBM Austin Research Laboratory, instanceOf, IBM research facility]
-
A.
IBM facility
chosen
An IBM facility is a physical location owned or operated by IBM where the company conducts its business activities, such as research, development, manufacturing, data center operations, or corporate services.
-
B.
IBM research project
An IBM research project is a structured, exploratory initiative undertaken by IBM Research to investigate advanced technologies, develop innovative solutions, and generate new scientific or technical knowledge aligned with IBM’s strategic goals.
-
C.
IBM organization
An IBM organization is a structured business entity or unit within IBM that coordinates people, resources, and processes to deliver specific products, services, or strategic outcomes aligned with the company’s overall goals.
-
D.
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.
-
E.
Microsoft research lab
A Microsoft research lab is a specialized facility where scientists and engineers conduct advanced research in computer science and related fields to develop innovative technologies and solutions for Microsoft and the broader tech community.
- 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:19 p.m.