Triple
T5421971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Insurance Service |
E121272
|
entity |
| Predicate | eligibleBeneficiaries |
P63569
|
FINISHED |
| Object | veterans |
—
|
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: veterans | Statement: [Insurance Service, eligibleBeneficiaries, veterans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleBeneficiaries Context triple: [Insurance Service, eligibleBeneficiaries, veterans]
-
A.
beneficiaries
Indicates that certain entities receive advantages, profits, or positive outcomes from an action, event, or arrangement.
-
B.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
-
C.
primaryBeneficiaries
Indicates which entities are the main recipients or advantaged parties resulting from a particular action, resource, or arrangement.
-
D.
eligibleFamilies
Indicates that certain families meet the required criteria or conditions to qualify for a specified benefit, service, or program.
-
E.
beneficiaryRequirement
Indicates that one entity has a requirement specifying who or what must be the beneficiary of a particular action, service, or resource.
- F. None of above. chosen
Provenance (4 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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87ec45c48190a8a25bf582b02440 |
completed | March 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8741e8588190863fd5cfb559136d |
completed | March 20, 2026, 5:43 p.m. |
Created at: March 20, 2026, 2:06 p.m.