Triple
T16835373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Investigation Team (MH17) |
E409261
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint investigation team |
C2354
|
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: joint investigation team Context triple: [Joint Investigation Team (MH17), instanceOf, joint investigation team]
-
A.
investigative journalism team
An investigative journalism team is a collaborative group of reporters, editors, and researchers who systematically uncover, verify, and report hidden or complex information in the public interest.
-
B.
human rights investigation team
A human rights investigation team is a specialized group that systematically collects, analyzes, and documents evidence of alleged human rights violations to establish facts, support accountability, and inform advocacy or legal action.
-
C.
criminal investigation unit
chosen
A criminal investigation unit is a specialized law enforcement team responsible for systematically gathering, analyzing, and preserving evidence to identify suspects, solve crimes, and support successful prosecution.
-
D.
investigative agency
An investigative agency is an organized entity that conducts systematic inquiries and gathers evidence to uncover facts, resolve disputes, or support legal and security-related decisions.
-
E.
joint institute
A joint institute is an educational or research organization formed through a formal partnership between two or more institutions, typically across regions or countries, to collaboratively share resources, expertise, and programs.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
Created at: April 10, 2026, 5:23 a.m.