Triple
T7338563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conway–Norton collaboration |
E169190
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mathematical collaboration |
C22014
|
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: mathematical collaboration Context triple: [Conway–Norton collaboration, instanceOf, mathematical collaboration]
-
A.
mathematical work
A mathematical work is a structured intellectual creation that develops, analyzes, or communicates mathematical concepts, results, or methods, typically through definitions, theorems, proofs, and examples.
-
B.
scientific collaboration board
A scientific collaboration board is a shared digital or physical workspace where researchers coordinate projects, exchange data and ideas, track progress, and manage collaborative tasks across institutions and disciplines.
-
C.
university collaboration
University collaboration is the structured partnership between universities and external entities (such as other academic institutions, industry, government, or communities) to jointly pursue research, education, innovation, and resource sharing.
-
D.
collaborative networks
Collaborative networks are interconnected groups of individuals or organizations that share resources, knowledge, and responsibilities to achieve common goals more effectively than they could independently.
-
E.
mathematics department
A mathematics department is an academic unit within an educational institution responsible for teaching, research, and scholarly activities in the field of mathematics and its applications.
- 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:04 p.m.