Triple
T15515063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. nationals |
E368813
|
entity |
| Predicate | areEligibleFor |
P84
|
FINISHED |
| Object | some federal 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: some federal benefits | Statement: [U.S. nationals, areEligibleFor, some federal benefits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areEligibleFor Context triple: [U.S. nationals, areEligibleFor, some federal benefits]
-
A.
alsoEligible
Indicates that an entity qualifies for an additional option, status, or benefit beyond its primary or initial eligibility.
-
B.
eligibility
chosen
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
C.
eligibleOn
Indicates the date or condition from which something qualifies to begin or be considered valid or applicable.
-
D.
positionEligible
Indicates that an entity is qualified or permitted to hold or be assigned to a particular position or role.
-
E.
eligibleIn
Indicates that an entity meets the necessary conditions or criteria to qualify for participation, use, or consideration within a specified context, domain, or scope.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04031e62c8190953b61207142af15 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:02 a.m.