Triple
T2277051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Physical Sciences Laboratory |
E51194
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | atmospheric research organization |
C656
|
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: atmospheric research organization Context triple: [Physical Sciences Laboratory, instanceOf, atmospheric research organization]
-
A.
aerospace organization
An aerospace organization is an entity that researches, designs, manufactures, operates, or supports aircraft, spacecraft, and related systems and technologies for commercial, governmental, or defense purposes.
-
B.
research and development organization
A research and development organization is an entity dedicated to systematically investigating ideas and technologies to create new knowledge, products, or processes and improve existing ones.
-
C.
meteorological organization
chosen
A meteorological organization is an entity responsible for observing, analyzing, and forecasting atmospheric conditions to support weather prediction, climate monitoring, and related public and scientific services.
-
D.
research organization
A research organization is an institution that systematically investigates specific questions or problems to generate new knowledge, technologies, or insights, often within scientific, academic, or applied domains.
-
E.
public research institution
A public research institution is a government-funded organization dedicated to advancing knowledge and innovation through systematic investigation, experimentation, and dissemination of findings for the benefit of society.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
Created at: March 4, 2026, 7:48 p.m.