Triple
T449620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Research and Development |
E7097
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research administration office |
C1214
|
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: research administration office Context triple: [Office of Research and Development, instanceOf, research administration office]
-
A.
academic administrator
An academic administrator is a professional responsible for planning, organizing, and overseeing the non-teaching operations and policies of educational institutions to support their academic mission.
-
B.
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.
-
C.
research facility
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 grant program
A research grant program is a structured funding initiative that provides financial support to researchers or institutions to conduct specific scholarly, scientific, or creative projects aligned with defined goals and priorities.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.