Triple
T1979426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team KAIST |
E42990
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university-affiliated research team |
C4221
|
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: university-affiliated research team Context triple: [Team KAIST, instanceOf, university-affiliated research team]
-
A.
university research team
chosen
A university research team is a collaborative group of faculty, students, and sometimes external partners who systematically investigate specific academic or scientific questions to generate new knowledge and publish their findings.
-
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 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.
-
D.
research consortium
A research consortium is a collaborative alliance of multiple organizations or institutions that pool resources, expertise, and infrastructure to conduct joint research toward shared scientific or technological goals.
-
E.
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.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:36 p.m.