Triple
T25964026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Assault Weapons Ban |
E645614
|
entity |
| Predicate | capacityThresholdForMagazines |
P159607
|
FINISHED |
| Object | more than 10 rounds |
—
|
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: more than 10 rounds | Statement: [Federal Assault Weapons Ban, capacityThresholdForMagazines, more than 10 rounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityThresholdForMagazines Context triple: [Federal Assault Weapons Ban, capacityThresholdForMagazines, more than 10 rounds]
-
A.
compatibleMagazines
Indicates that two magazines can be used together or interchangeably without conflict or issues.
-
B.
aircraftMagazineCapacity
Indicates the maximum number of rounds or munitions an aircraft’s weapon magazine can hold.
-
C.
hasMagazineType
Indicates that an entity is associated with, or classified by, a specific type or category of magazine.
-
D.
ownedMagazinePortfolioSize
Indicates the number of magazines included in an entity’s owned magazine portfolio.
-
E.
hasMagazine
Indicates that one entity possesses, contains, or is equipped with a magazine (such as a periodical or an ammunition magazine).
- F. None of above. chosen
Provenance (4 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f604c8ef408190bfd4571fb262372b |
completed | May 2, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:48 a.m.