Triple
T30518692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | trung tâm nghiên cứu lịch sử và bảo tồn di sản |
E776634
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tổ chức nghiên cứu |
C187
|
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: tổ chức nghiên cứu Context triple: [trung tâm nghiên cứu lịch sử và bảo tồn di sản, instanceOf, tổ chức nghiên cứu]
-
A.
research organization
chosen
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.
-
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 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.
-
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 unit
A research unit is an organized group within an institution dedicated to conducting systematic investigations, generating new knowledge, and supporting scholarly or scientific inquiry in specific fields or interdisciplinary areas.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:16 p.m.