Triple
T37784758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Havasupai Tribe v. Arizona State University |
E941922
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | human subjects research controversy |
C33575
|
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: human subjects research controversy Context triple: [Havasupai Tribe v. Arizona State University, instanceOf, human subjects research controversy]
-
A.
research ethics case
chosen
A research ethics case is a detailed scenario or incident that illustrates ethical dilemmas, conflicts, or decision points arising in the design, conduct, or reporting of research involving human or animal subjects, data, or broader societal impacts.
-
B.
public policy controversy
A public policy controversy is a sustained, often polarized dispute among stakeholders over the goals, design, implementation, or consequences of government actions or regulations.
-
C.
human experimentation program
A human experimentation program is an organized initiative that systematically conducts research or testing on human subjects to study biological, psychological, or behavioral effects under controlled conditions.
-
D.
bioethics department
A bioethics department is an organizational unit that studies, advises on, and develops policies regarding the ethical, legal, and social implications of biological and medical research, healthcare practices, and life sciences technologies.
-
E.
medical-ethics case
A medical-ethics case is a detailed account of a real or hypothetical clinical situation that raises moral questions about patient care, professional duties, and healthcare decision-making.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.