Triple
T7846190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form 1099-NEC |
E181927
|
entity |
| Predicate | eFilingAllowed |
P12649
|
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: [Form 1099-NEC, eFilingAllowed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eFilingAllowed Context triple: [Form 1099-NEC, eFilingAllowed, true]
-
A.
hasCaseFilingRequirement
Indicates that an entity is subject to a requirement to file or submit a formal legal case or case-related documents.
-
B.
filedWith
Indicates that one entity has officially submitted or registered something (such as a document, complaint, or application) to another entity or authority.
-
C.
filingMethod
chosen
Indicates how a document, record, or information is submitted or recorded, such as the process, channel, or format used for filing.
-
D.
placeOfFiling
Indicates the location or jurisdiction where a legal document, case, or claim is formally submitted or recorded.
-
E.
filingForm
Indicates that an entity submits or completes a specific form or document, typically as part of an official or administrative process.
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb163f5da08190b7340ef4cc01cd19 |
completed | March 31, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:49 p.m.