Triple
T8998847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Structural Studies Division |
E214990
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scientific research unit |
C63
|
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: scientific research unit Context triple: [Structural Studies Division, instanceOf, scientific research unit]
-
A.
multidisciplinary research unit
A multidisciplinary research unit is an organized group that integrates expertise, methods, and perspectives from multiple academic or professional fields to collaboratively investigate complex problems and generate comprehensive insights.
-
B.
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.
-
C.
research facility
chosen
A research facility is a specialized institution equipped with laboratories, instruments, and resources where scientists and experts systematically investigate, experiment, and develop new knowledge or technologies.
-
D.
research university
A research university is a higher education institution that prioritizes the creation of new knowledge through extensive research activities while offering a broad range of undergraduate and graduate academic programs.
-
E.
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.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:05 p.m.