Triple
T5421804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compensation Service |
E121268
|
entity |
| Predicate | eligibilityCriteriaIncludes |
P1130
|
FINISHED |
| Object | veteran status |
—
|
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: veteran status | Statement: [Compensation Service, eligibilityCriteriaIncludes, veteran status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibilityCriteriaIncludes Context triple: [Compensation Service, eligibilityCriteriaIncludes, veteran status]
-
A.
eligibilityCriteria
chosen
Indicates the conditions or requirements that must be satisfied for an entity to qualify for or be considered eligible for something.
-
B.
eligibilityCategory
Indicates the classification or type of eligibility that applies to an entity within a given context.
-
C.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
-
D.
eligibilityContext
Indicates the situational or conditional factors under which an entity qualifies for or is considered eligible for something.
-
E.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
- 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_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. |
Created at: March 20, 2026, 2:06 p.m.