Triple
T16823482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harold L. Volkmer |
E408954
|
entity |
| Predicate | legislative interest |
P8905
|
FINISHED |
| Object | firearms regulation |
—
|
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 regulation | Statement: [Harold L. Volkmer, legislative interest, firearms regulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislative interest Context triple: [Harold L. Volkmer, legislative interest, firearms regulation]
-
A.
legislativeImpact
Indicates the effect that a law or legislative action has on a policy, entity, or outcome.
-
B.
hasLegislativeSubject
chosen
Indicates that a legislative document, action, or body concerns, addresses, or is about a particular subject or topic.
-
C.
legislature
Indicates that an entity serves as, or is part of, a law-making body or assembly responsible for creating or amending laws for a political unit.
-
D.
areaOfLegislation
Indicates that one entity defines, concerns, or governs the legal domain or subject matter covered by another entity.
-
E.
relatedLegislation
Indicates that there exists a legislative document that is connected to, affects, or is otherwise relevant to the subject entity.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e838e881908b650194c9b94886 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.