Triple
T7846188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form 1099-NEC |
E181927
|
entity |
| Predicate | recipientCopyDeadline |
P8546
|
FINISHED |
| Object | January 31 |
—
|
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: January 31 | Statement: [Form 1099-NEC, recipientCopyDeadline, January 31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recipientCopyDeadline Context triple: [Form 1099-NEC, recipientCopyDeadline, January 31]
-
A.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
-
B.
hasDeadline
chosen
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
-
C.
mustBeDeliveredBy
Indicates that one entity is required to be delivered or completed no later than a specified time, date, or deadline set by another entity.
-
D.
dateReceived
Indicates the point in time when something (such as a message, item, or document) was received by a recipient.
-
E.
dateSent
Indicates the specific date on which something (such as a message, document, or item) was sent from one party to another.
- 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.