Triple
T20952152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maguire Seven case |
E516005
|
entity |
| Predicate | forensicIssue |
P29037
|
FINISHED |
| Object | contaminated samples |
—
|
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: contaminated samples | Statement: [Maguire Seven case, forensicIssue, contaminated samples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forensicIssue Context triple: [Maguire Seven case, forensicIssue, contaminated samples]
-
A.
hasForensicElement
Indicates that something includes, involves, or is characterized by a forensic component, aspect, or feature.
-
B.
involvesIssue
chosen
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
-
C.
subjectOfInquest
Indicates that an entity is the focus or target of a formal inquest or official investigative proceeding.
-
D.
frameForCrime
Indicates causing someone to be falsely perceived or officially treated as responsible for a crime they did not commit.
-
E.
recognitionOfCrimes
Indicates the formal acknowledgment or identification that certain actions or events constitute crimes under a legal or normative framework.
- 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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fade4e2c81908ab2619d74fcc5a7 |
completed | April 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 1:27 p.m.