Triple
T13289856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSCE Conflict Prevention Centre |
E316538
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | CSCE institution |
C32781
|
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: CSCE institution Context triple: [CSCE Conflict Prevention Centre, instanceOf, CSCE institution]
-
A.
science and engineering campus
A science and engineering campus is a specialized academic environment that concentrates facilities, laboratories, and resources to support education and research in scientific and engineering disciplines.
-
B.
computer science school
A computer science school is an educational institution or program dedicated to teaching the principles, theories, and practical skills of computing, programming, and information technology.
-
C.
Purdue University college
A Purdue University college is an academic division within Purdue University that organizes related departments and programs to provide specialized education, research, and outreach in a particular field of study.
-
D.
Texas A&M University unit
A Texas A&M University unit is an organizational entity within the university—such as a college, department, division, or administrative office—responsible for specific academic, research, service, or operational functions.
-
E.
college of North Carolina State University
A college of North Carolina State University is an academic division within the university that organizes related departments and programs to provide specialized education, research, and outreach in a particular field of study.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:27 p.m.