Triple
T13889439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPS-1 |
E333930
|
entity |
| Predicate | benefitCharacteristic |
P111885
|
FINISHED |
| Object | minimum benefits in BPS system |
—
|
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: minimum benefits in BPS system | Statement: [BPS-1, benefitCharacteristic, minimum benefits in BPS system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitCharacteristic Context triple: [BPS-1, benefitCharacteristic, minimum benefits in BPS system]
-
A.
benefitAppliesTo
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
-
B.
benefitsAre
Indicates that certain advantages, gains, or positive outcomes are possessed by or accrue to a particular entity or group.
-
C.
primaryBenefit
Indicates that one entity serves as the main or most important advantage, gain, or positive outcome associated with another entity.
-
D.
benefice
Indicates that one entity grants or bestows a benefit, favor, or advantage upon another.
-
E.
benefits
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a3a24881908d81d634622fbbcc |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
| PDg | Predicate description generation | batch_69de01ed2098819088ec45069f6f2609 |
completed | April 14, 2026, 8:59 a.m. |
Created at: April 9, 2026, 10:15 p.m.