Triple
T7846169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form W-3 |
E181926
|
entity |
| Predicate | instructionDocument |
P32295
|
FINISHED |
| Object | General Instructions for Forms W-2 and W-3 |
—
|
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: General Instructions for Forms W-2 and W-3 | Statement: [Form W-3, instructionDocument, General Instructions for Forms W-2 and W-3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instructionDocument Context triple: [Form W-3, instructionDocument, General Instructions for Forms W-2 and W-3]
-
A.
instruction
Indicates that one entity provides a directive or order specifying an action that another entity should perform.
-
B.
documentationUI
Indicates a relationship where a user interface element is used to present, navigate, or interact with documentation content.
-
C.
movementDocumented
Indicates that the movement or transfer of an entity from one place or state to another has been formally recorded or documented.
-
D.
usageInstruction
chosen
Indicates that one entity provides guidance or directions on how to properly use, operate, or handle another entity.
-
E.
programDocument
Indicates that a document is associated with, defines, or describes a particular program (such as a software application, project, or initiative).
- 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.