Triple
T38526751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATF forensic laboratories |
E923247
|
entity |
| Predicate | typeOfEvidenceHandled |
P172641
|
FINISHED |
| Object | firearms |
—
|
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: firearms | Statement: [ATF forensic laboratories, typeOfEvidenceHandled, firearms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEvidenceHandled Context triple: [ATF forensic laboratories, typeOfEvidenceHandled, firearms]
-
A.
evidenceTypeHandled
chosen
Indicates that an entity is responsible for processing or managing a particular type or category of evidence.
-
B.
evidenceHandling
Indicates how evidence is collected, processed, stored, and transferred within an investigation or legal context.
-
C.
usedEvidenceType
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
-
D.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
E.
evidenceAtIssue
Indicates that a particular piece of evidence is directly contested, disputed, or central to the disagreement or decision in a case or situation.
- 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.