Triple
T2478481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Firearms Licensees |
E55145
|
entity |
| Predicate | penaltyForViolation |
P36372
|
FINISHED |
| Object | license revocation |
—
|
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: license revocation | Statement: [Federal Firearms Licensees, penaltyForViolation, license revocation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: penaltyForViolation Context triple: [Federal Firearms Licensees, penaltyForViolation, license revocation]
-
A.
penaltyProvision
Indicates that a rule, contract, or law includes a clause specifying a punishment or sanction for non-compliance or violation.
-
B.
violationConsequences
chosen
Indicates the negative outcomes, penalties, or repercussions that result from a violation of a rule, law, or agreement.
-
C.
violationOf
Indicates that one entity breaches, disobeys, or infringes upon a rule, law, agreement, or right associated with another entity.
-
D.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
E.
hasPunishment
Indicates that an entity is subject to a specified penalty, sanction, or adverse consequence as a result of some action, condition, or rule.
- 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_69ab49e279e88190ab10d7248aea9d11 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd1eb3be481908fa7c6b8f1c78209 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b5e3d481909a5cbc4a96edd24f |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.