Triple
T27899620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schedule SE (Form 1040) |
E705591
|
entity |
| Predicate | outputUsedOn |
P2367
|
FINISHED |
| Object | Form 1040, Schedule 2 |
—
|
NE NERFINISHED |
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: Form 1040, Schedule 2 | Statement: [Schedule SE (Form 1040), outputUsedOn, Form 1040, Schedule 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputUsedOn Context triple: [Schedule SE (Form 1040), outputUsedOn, Form 1040, Schedule 2]
-
A.
outputUsedBy
Indicates that a particular output produced by one entity is consumed, referenced, or otherwise utilized by another entity.
-
B.
usedOn
chosen
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
C.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
D.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
wasUsedBy
Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 6:41 p.m.