Triple
T37976461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRS Form 720 |
E947436
|
entity |
| Predicate | filingObligationTrigger |
P132544
|
FINISHED |
| Object | liability for certain federal excise taxes |
—
|
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: liability for certain federal excise taxes | Statement: [IRS Form 720, filingObligationTrigger, liability for certain federal excise taxes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filingObligationTrigger Context triple: [IRS Form 720, filingObligationTrigger, liability for certain federal excise taxes]
-
A.
filingObligation
chosen
Indicates that an entity is required to submit specified documents or reports to an authority within defined conditions or timeframes.
-
B.
filingTypeCode
Indicates the specific category or type of filing associated with a submitted document or record.
-
C.
permitsFilingIn
Indicates that one entity authorizes or allows another entity to submit or initiate a filing within its jurisdiction, system, or process.
-
D.
filingStage
Indicates the procedural phase or step that a filing or submission is currently in within a formal process or workflow.
-
E.
filingMethod
Indicates how a document, record, or information is submitted or recorded, such as the process, channel, or format used for filing.
- 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.