Triple
T7846164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form W-3 |
E181926
|
entity |
| Predicate | requiresAttachment |
P63443
|
FINISHED |
| Object | Copy A of all Forms W-2 |
—
|
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: Copy A of all Forms W-2 | Statement: [Form W-3, requiresAttachment, Copy A of all Forms W-2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresAttachment Context triple: [Form W-3, requiresAttachment, Copy A of all Forms W-2]
-
A.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
B.
requiresDispositionOf
Indicates that one entity must be appropriately handled, removed, or otherwise disposed of as a condition related to another entity or situation.
-
C.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
D.
requiresDocument
chosen
Indicates that one entity can only proceed, be valid, or be completed if a specified document is provided or present.
-
E.
requiresProofOf
Indicates that one entity must provide formal evidence or documentation to validate or authorize another entity.
- 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.