Triple
T7846108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form 1040-NR filing |
E181925
|
entity |
| Predicate | doesNotExtend |
P10124
|
FINISHED |
| Object | time to pay tax due |
—
|
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: time to pay tax due | Statement: [Form 1040-NR filing, doesNotExtend, time to pay tax due]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotExtend Context triple: [Form 1040-NR filing, doesNotExtend, time to pay tax due]
-
A.
doesNotDefine
Indicates that one entity does not provide a definition, specification, or determining description for another entity.
-
B.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
C.
doesNotUse
Indicates that one entity intentionally refrains from employing, utilizing, or relying on another entity, method, or resource.
-
D.
notDerivedFrom
Indicates that one entity is explicitly not obtained, inferred, or produced from another entity.
-
E.
doesNotCover
chosen
Indicates that one entity fails to include, protect, or extend over another entity or area.
- 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.