Triple
T7846092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form 1040-NR filing |
E181925
|
entity |
| Predicate | mayClaim |
P16619
|
FINISHED |
| Object | tax treaty benefits |
—
|
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: tax treaty benefits | Statement: [Form 1040-NR filing, mayClaim, tax treaty benefits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayClaim Context triple: [Form 1040-NR filing, mayClaim, tax treaty benefits]
-
A.
mainClaim
Indicates that one statement is presented as the central or primary assertion being made about a topic.
-
B.
modalClaim
chosen
Indicates that the statement is being made with a modal qualification, such as possibility, necessity, or obligation, rather than as an unqualified factual claim.
-
C.
mayCover
Indicates that one entity is permitted or able to extend over, include, or provide coverage for another entity, either partially or fully.
-
D.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
E.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to 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.