Triple
T32619482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sole Survivor Policy |
E833880
|
entity |
| Predicate | canBeWaivedBy |
P68180
|
FINISHED |
| Object | service member |
—
|
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: service member | Statement: [Sole Survivor Policy, canBeWaivedBy, service member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeWaivedBy Context triple: [Sole Survivor Policy, canBeWaivedBy, service member]
-
A.
providesExemptionsTo
chosen
Indicates that one entity grants or offers exemptions, waivers, or exceptions from rules, obligations, or requirements to another entity.
-
B.
canBeAppealedTo
Indicates that a decision, action, or authority is subject to being challenged or reviewed by a higher or alternative authority through an appeal process.
-
C.
canBeAwarded
Indicates that an entity is eligible to receive or be granted a particular award, prize, or honor.
-
D.
standardOfWaiver
Indicates the legal criteria or conditions under which a right, claim, or requirement can be voluntarily relinquished or waived.
-
E.
canAward
Indicates that one entity has the authority or ability to grant an award, honor, or recognition to another entity.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: May 1, 2026, 1:06 a.m.