Triple
T13224202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Director of the Loker Hydrocarbon Research Institute |
E314832
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | head of research institute |
C9273
|
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: head of research institute Context triple: [Director of the Loker Hydrocarbon Research Institute, instanceOf, head of research institute]
-
A.
director of research institution
chosen
A director of a research institution is the senior leader responsible for setting the organization’s scientific vision, securing funding, overseeing research programs and staff, and ensuring the institution’s work advances knowledge and meets strategic goals.
-
B.
library scientist
A library scientist is an information professional who organizes, manages, and curates collections and data systems to ensure efficient access, preservation, and use of knowledge resources.
-
C.
researcher
A researcher is an individual who systematically investigates questions or problems using structured methods to generate new knowledge, validate existing theories, or develop practical solutions.
-
D.
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.
-
E.
academic chair
An academic chair is a senior faculty position, often endowed, that provides leadership in a specific discipline through teaching, research, and service within a higher education institution.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:19 p.m.