Triple
T16835399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Investigation Team (MH17) |
E409261
|
entity |
| Predicate | collectsEvidenceType |
P3168
|
FINISHED |
| Object | forensic evidence |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: forensic evidence | Statement: [Joint Investigation Team (MH17), collectsEvidenceType, forensic evidence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectsEvidenceType Context triple: [Joint Investigation Team (MH17), collectsEvidenceType, forensic evidence]
-
A.
usedEvidenceType
chosen
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
-
B.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
C.
detectiveType
Indicates that one entity is classified as a particular type or category of detective in relation to another entity.
-
D.
mayHearEvidenceFrom
Indicates that an authority or decision-maker is permitted to receive and consider evidence presented by a specified source.
-
E.
hasMaterialEvidence
Indicates that there exists tangible, physical evidence supporting or associated with a particular entity, event, or claim.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69e3b31aa44c8190b4f402f1898e6998 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.