Triple
T33555790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM Cambridge Scientific Center |
E859469
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IBM research and development 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 and development facility Context triple: [IBM Cambridge Scientific Center, instanceOf, IBM research and development 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.
U.S. federal research facility
A U.S. federal research facility is a government-operated institution dedicated to conducting scientific, technical, or policy research in support of national priorities, public welfare, and informed decision-making.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:40 a.m.