Triple
T17226751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WMAP Team |
E418134
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cosmology collaboration |
C30283
|
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: cosmology collaboration Context triple: [WMAP Team, instanceOf, cosmology collaboration]
-
A.
astronomical research collaboration
chosen
An astronomical research collaboration is a coordinated partnership of scientists, institutions, and facilities that jointly design, conduct, and analyze observations and experiments to advance understanding of the universe.
-
B.
cosmology experiment
A cosmology experiment is a scientific investigation designed to measure and analyze cosmic phenomena—such as the cosmic microwave background, large-scale structure, or dark energy—to test and refine models of the universe’s origin, composition, and evolution.
-
C.
cosmological realm
A cosmological realm is a vast, often metaphysical domain or layer of existence within the universe or multiverse, defined by its own fundamental laws, structures, and cosmic entities.
-
D.
cosmology paper
A cosmology paper is a scholarly article that presents theoretical models, observational analyses, or simulations to investigate the origin, structure, evolution, and large-scale properties of the universe.
-
E.
particle physics collaboration
A particle physics collaboration is a large, often international team of scientists, engineers, and institutions that jointly design, build, operate, and analyze experiments to study fundamental particles and their interactions.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:39 a.m.