Triple
T32766364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SP5 (civilian variant) |
E837912
|
entity |
| Predicate | intendedToComplyWith |
P186691
|
FINISHED |
| Object | non-military firearm regulations |
—
|
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: non-military firearm regulations | Statement: [SP5 (civilian variant), intendedToComplyWith, non-military firearm regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedToComplyWith Context triple: [SP5 (civilian variant), intendedToComplyWith, non-military firearm regulations]
-
A.
indicatesComplianceWith
Indicates that one entity conforms to, satisfies, or adheres to the rules, standards, or requirements specified by another entity or framework.
-
B.
mayComplyWith
chosen
Indicates that an entity is permitted or has the option to adhere to, follow, or satisfy a specified rule, standard, or requirement.
-
C.
regulatesComplianceWith
Indicates that one entity oversees, enforces, or sets rules to ensure another entity adheres to specified standards, laws, or requirements.
-
D.
hasComplianceStatement
Indicates that an entity is associated with a formal declaration that it adheres to specified rules, standards, or regulatory requirements.
-
E.
complianceInstrument
Indicates that one entity serves as a tool, mechanism, or measure used to ensure, demonstrate, or enforce compliance with a rule, standard, or obligation for another 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 1, 2026, 1:13 a.m.