Triple
T25964040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Assault Weapons Ban |
E645614
|
entity |
| Predicate | hadSunsetProvision |
P7904
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Federal Assault Weapons Ban, hadSunsetProvision, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSunsetProvision Context triple: [Federal Assault Weapons Ban, hadSunsetProvision, true]
-
A.
containsSunsetProvisions
chosen
Indicates that an agreement, law, or contract includes clauses that cause some or all of its provisions to expire or terminate automatically at a specified future time unless renewed or extended.
-
B.
hasSunsetView
Indicates that one entity offers a clear or notable view of the sunset from its location or perspective.
-
C.
sunsetAnnounced
Indicates that an announcement has been made stating that a particular sunset event is occurring or will occur.
-
D.
hasSunriseView
Indicates that a location or object offers a clear or notable view of the sunrise.
-
E.
hasSolarTransition
Indicates a relationship where an entity undergoes or is associated with a change or shift in solar-related conditions, states, or configurations.
- 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_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. |
Created at: April 22, 2026, 8:48 a.m.