Triple
T36977594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Other Dependent Credit |
E914741
|
entity |
| Predicate | eligibleDependentType |
P83633
|
FINISHED |
| Object | qualifying relative |
—
|
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: qualifying relative | Statement: [Other Dependent Credit, eligibleDependentType, qualifying relative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleDependentType Context triple: [Other Dependent Credit, eligibleDependentType, qualifying relative]
-
A.
eligibleFamily
Indicates that one entity qualifies as a family member of another under specified eligibility rules or criteria.
-
B.
isAidDependent
Indicates that one entity’s functioning, survival, or development relies significantly on receiving aid or assistance from another entity.
-
C.
eligiblePersons
chosen
Indicates that certain persons meet the required conditions or criteria to qualify for a particular status, benefit, or participation.
-
D.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
-
E.
eligibleBeneficiaries
Indicates that certain parties meet the required conditions to receive benefits or entitlements under a given rule or program.
- 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_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.