Triple
T36977601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Other Dependent Credit |
E914741
|
entity |
| Predicate | requiresDependentToBeClaimedOn |
P41193
|
FINISHED |
| Object | Form 1040 |
—
|
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 | Statement: [Other Dependent Credit, requiresDependentToBeClaimedOn, Form 1040]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresDependentToBeClaimedOn Context triple: [Other Dependent Credit, requiresDependentToBeClaimedOn, Form 1040]
-
A.
requiresDependentToHave
Indicates that one entity’s validity or operation is contingent on another entity possessing a specified attribute, state, or condition.
-
B.
requiresClaim
chosen
Indicates that one entity can only be accessed, used, or fulfilled if a specific claim or entitlement has first been asserted or verified.
-
C.
hasClaimOn
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
-
D.
statusDependsOn
Indicates that the status or state of one entity is determined or influenced by the status or state of another entity.
-
E.
alsoClaimedBy
Indicates that the same item, statement, or resource is asserted or claimed by an additional party besides the primary one.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
Created at: May 3, 2026, 4:14 p.m.