Triple
T12790519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inactive National Guard (historical) |
E305746
|
entity |
| Predicate | memberBenefits |
P101952
|
FINISHED |
| Object | no drill pay |
—
|
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: no drill pay | Statement: [Inactive National Guard (historical), memberBenefits, no drill pay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberBenefits Context triple: [Inactive National Guard (historical), memberBenefits, no drill pay]
-
A.
benefitsAre
Indicates that certain advantages, gains, or positive outcomes are possessed by or accrue to a particular entity or group.
-
B.
benefits
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
C.
benefitAppliesTo
chosen
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
-
D.
hasBenefit
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
E.
beneficialMembers
Indicates that certain members of a group have a positive or advantageous effect on the group or on other entities.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6a61f48190972e241e70bc392c |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.